Get the comprehensive usage guide for project-graph with examples and best practices.\nCall this FIRST when planning how to analyze, navigate, or audit a codebase.\nReturns practical examples and recommended workflow for each feature area.\n\nAvailable topics: navigation, analysis, testing, docum...
AI agents call get_usage_guide to retrieve information from Project Graph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves documentation and guidance information without side effects. It is purely informational, similar to fetching help documentation or reading a guide. There is no capability to modify data, execute code, delete content, or trigger external operations. The severity is low because misuse would only result in an agent obtaining documentation that is publicly intended for users.
From the tool's definition Tool retrieves and returns documentation: 'Get the comprehensive usage guide', 'Returns practical examples and recommended workflow'. No modification, deletion, or execution capabilities described.
Attacks that exploit this kind of access
Get the comprehensive usage guide for project-graph with examples and best practices.\nCall this FIRST when planning how to analyze, navigate, or audit a codebase.\nReturns practical examples and recommended workflow for each feature area.\n\nAvailable topics: navigation, analysis, testing, documentation, rules, workflow.\nOmit topic to get the full guide. It is categorised as a Read tool in the Project Graph MCP Server, which means it retrieves data without modifying state.
Register the Project Graph MCP server in PolicyLayer and add a rule for get_usage_guide: 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 Project Graph. Nothing to install.
get_usage_guide 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_usage_guide 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_usage_guide. 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_usage_guide is provided by the Project Graph MCP server (rnd-pro/project-graph-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 →