List recent tool, Slack API, or access-control failures from local diagnostics state.
AI agents call ops_recent_failures to retrieve information from Slack Max API MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists historical failure information from local diagnostics state. It has no side effects—it only queries and returns data about past failures. This is a read-only diagnostic operation that does not create, modify, delete, or execute anything.
From the tool's definition Tool name 'ops_recent_failures' and description 'List recent tool, Slack API, or access-control failures from local diagnostics state' indicate retrieval of diagnostic/failure logs with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List recent tool, Slack API, or access-control failures from local diagnostics state. It is categorised as a Read tool in the Slack Max API MCP MCP Server, which means it retrieves data without modifying state.
Register the Slack Max API MCP server in PolicyLayer and add a rule for ops_recent_failures: 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 Slack Max API MCP. Nothing to install.
ops_recent_failures 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 ops_recent_failures 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 ops_recent_failures. 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.
ops_recent_failures is provided by the Slack Max API MCP server (jeongwoobin335/slack-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 →