Describe what this MCP server can do and how to use it. Call this when the user asks
AI agents call describe_capabilities to retrieve information from Stepsecurity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though describe_capabilities only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Describe what this MCP server can do and how to use it. Call this when the user asks. It is categorised as a Read tool in the Stepsecurity MCP Server, which means it retrieves data without modifying state.
Register the Stepsecurity MCP server in PolicyLayer and add a rule for describe_capabilities: 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 Stepsecurity. Nothing to install.
describe_capabilities 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 describe_capabilities 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 describe_capabilities. 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.
describe_capabilities is provided by the Stepsecurity MCP server (step-security/stepsecurity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.