Generate deployment reports
AI agents call create_deployment_summary to retrieve information from Terragrunt GCP Tool MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Creating a deployment summary/report is a read-oriented operation that aggregates and presents existing deployment data. It does not modify infrastructure, execute commands, or delete resources. The word 'Generate' in context of 'reports' strongly suggests a read/summarize operation. Severity is low as misuse would at most expose deployment information.
From the tool's definition 'Generate deployment reports' — reporting/summarization implies reading and presenting existing data without side effects.
Attacks that exploit this kind of access
Generate deployment reports. It is categorised as a Read tool in the Terragrunt GCP Tool MCP MCP Server, which means it retrieves data without modifying state.
Register the Terragrunt GCP Tool MCP server in PolicyLayer and add a rule for create_deployment_summary: 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 Terragrunt GCP Tool MCP. Nothing to install.
create_deployment_summary 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 create_deployment_summary 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 create_deployment_summary. 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.
create_deployment_summary is provided by the Terragrunt GCP Tool MCP server (spolspol/terragrunt-gcp-tool-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →