A city 311 agent can call refund, reopen-case, and email-resident tools under one broad OAuth scope. What should security require?
Select an answer to reveal the explanation.
Short Explanation
One master key for refunds, reopen, and email is how a helpful 311 bot becomes a roaming cash drawer. Split the OAuth scopes so each tool only gets what it needs. Broad scopes are convenience until the first prompt-injection ride-along.
Full Explanation
A city 311 agent that can call refund, reopen-case, and email-resident tools under one broad OAuth scope concentrates excessive privilege into a single credential surface. Security should require separate least-privilege scopes so each tool receives only the rights it needs for its civic function. That way a compromised or misdirected refund call cannot also reopen cases or spam residents, and blast-radius for agent tool misuse stays limited to the intended municipal API.
Combining all 311 tools under a single municipal service-account password fails by concept: a shared password collapses authentication and authorization into one static secret, offers no per-tool scope separation, and typically cannot express fine-grained OAuth claims for refunds versus email. Disabling OAuth so the agent can call every civic API without tokens removes the control plane entirely and turns every tool invocation into an unauthenticated municipal integration. Publishing the agent’s refresh token in the resident chatbot FAQ is credential disclosure; public FAQ content is not a secrets vault and would let anyone replay agent API access.
Exam caveat: least-privilege scopes address authorization granularity for tools; they do not replace token storage hygiene, short lifetimes, or runtime allowlists that stop the model from requesting a tool it should never see. Operational check: inventory each 311 tool’s required API permissions, map distinct OAuth scopes or clients per tool (or per tool class), verify the agent runtime cannot obtain a refund-scoped token when only email is needed, and review audit logs for cross-scope calls during a controlled 311 refund drill.