AI agents use slack_notify to create or update resources in Git Steer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git Steer environment.
This tool creates (sends) a message/notification to Slack, which is a reversible action that modifies state in an external system (Slack channel history) but does not retrieve data (Read), execute arbitrary code (Execute), permanently delete data (Destructive), or move money (Financial). Message sending fits the Write category.
From the tool's definition The tool 'slack_notify' sends a notification to a Slack channel via webhook. The description explicitly states it is used for 'PR events, alerts, and remediation updates', which are notification-sending operations.
Attacks that exploit this kind of access
Send a notification to a Slack channel via webhook. Used for PR events, alerts, and remediation updates. It is categorised as a Write tool in the Git Steer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Git Steer MCP server in PolicyLayer and add a rule for slack_notify: 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 Git Steer. Nothing to install.
slack_notify 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 slack_notify 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 slack_notify. 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.
slack_notify is provided by the Git Steer MCP server (ry-ops/git-steer). 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 →