Send an end-of-day status update to a Slack channel. This tool automatically summarizes all work done by reviewing ALL conversations in your Cursor workspace for the specified date (defaults to today). When called without a summary parameter, it will automatically review all your conversations an...
AI agents use eod_status to create or update resources in Cursor EOD MCP (Slack) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cursor EOD MCP (Slack) environment.
This tool posts a message to a Slack channel, which is a reversible write operation (messages can be deleted). It also reads workspace conversations to generate the summary, but the primary action is posting to Slack. The blast radius is medium since it could expose workspace activity data to a Slack channel if misconfigured.
From the tool's definition Send an end-of-day status update to a Slack channel... formatted using your custom template and posted to Slack
Attacks that exploit this kind of access
Send an end-of-day status update to a Slack channel. This tool automatically summarizes all work done by reviewing ALL conversations in your Cursor workspace for the specified date (defaults to today). When called without a summary parameter, it will automatically review all your conversations and generate a comprehensive bullet-point summary of: work completed, issues resolved, features implemented, code changes made, and other significant activities. The summary is then formatted using your custom template and posted to Slack. Supports dynamic channel selection. It is categorised as a Write tool in the Cursor EOD MCP (Slack) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cursor EOD MCP (Slack) MCP server in PolicyLayer and add a rule for eod_status: 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 Cursor EOD MCP (Slack). Nothing to install.
eod_status 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 eod_status 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 eod_status. 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.
eod_status is provided by the Cursor EOD MCP (Slack) MCP server (sackeydavid/cursor-eod-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 →