AI agents call view_iam_policy to retrieve information from Storage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves policy data for inspection purposes only. It has no side effects, does not modify, delete, or execute any operations. It falls squarely into the Read category as it simply queries and returns existing IAM policy configuration.
From the tool's definition The tool 'view_iam_policy' with description 'Views the IAM policy for a bucket' performs a read-only operation to retrieve and display existing IAM policy information without modification.
Attacks that exploit this kind of access
Views the IAM policy for a bucket. It is categorised as a Read tool in the Storage MCP Server, which means it retrieves data without modifying state.
Register the Storage MCP server in PolicyLayer and add a rule for view_iam_policy: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Storage. Nothing to install.
view_iam_policy is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the view_iam_policy rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for view_iam_policy. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
view_iam_policy is provided by the Storage MCP server (@google-cloud/storage-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.