Send notifications to team
AI agents use send_slack_notification to create or update resources in Terragrunt GCP Tool MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Terragrunt GCP Tool MCP environment.
The tool sends messages/notifications to a Slack channel, which is a write operation (posting a message) with no destructive or financial implications. The severity is medium because a misconfigured or malicious notification could cause confusion, social engineering, or disrupt team operations.
From the tool's definition Send notifications to team
Attacks that exploit this kind of access
Send notifications to team. It is categorised as a Write tool in the Terragrunt GCP Tool MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Terragrunt GCP Tool MCP server in PolicyLayer and add a rule for send_slack_notification: 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.
send_slack_notification is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_slack_notification 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 send_slack_notification. 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.
send_slack_notification 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 →