get_capability_graph
Return a Capability Graph snapshot (nodes, shared-capability edges, capability index) for agent planning.
This record as markdown: /tools/404-directory/get-capability-graph.md
What get_capability_graph does on 404 Directory
AI agents call get_capability_graph 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 get_capability_graph is rated Low
Retrieves and returns read-only graph data for planning; no modifications or side effects.
From the tool's definition Return a Capability Graph snapshot for agent planning.
Attacks that exploit this kind of access
The rule that runs get_capability_graph 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 get_capability_graph, this is the rule to start with:
get_capability_graph 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 get_capability_graph call is checked against it from then on.
Questions about get_capability_graph
Return a Capability Graph snapshot (nodes, shared-capability edges, capability index) for agent planning. 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 get_capability_graph: 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.
get_capability_graph 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 get_capability_graph 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 get_capability_graph. 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.
get_capability_graph 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