list_capabilities
List capabilities in the 404 catalog with tool counts. Use to explore the Capability Graph before searching.
This record as markdown: /tools/404-directory/list-capabilities.md
What list_capabilities does on 404 Directory
AI agents call list_capabilities to retrieve information from 404 Directory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_capabilities is rated Low
Retrieves and queries catalog metadata without modification or side effects.
From the tool's definition List capabilities in the 404 catalog with tool counts. Use to explore.
Attacks that exploit this kind of access
The rule that runs list_capabilities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 404 Directory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_capabilities, this is the rule to start with:
list_capabilities is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 404 Directory, apply this rule, and every list_capabilities call is checked against it from then on.
Questions about list_capabilities
List capabilities in the 404 catalog with tool counts. Use to explore the Capability Graph before searching. It is categorised as a Read tool in the 404 Directory MCP Server, which means it retrieves data without modifying state.
Register the 404 Directory MCP server in PolicyLayer and add a rule for list_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 404 Directory. Nothing to install.
list_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 list_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 list_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.
list_capabilities is provided by the 404 Directory MCP server (MM-sheng/404-directory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 404 Directory, and thousands of servers like it.
This server
Across the catalogue