This record as markdown: /tools/io-github-devopam-mcpg/generate-graph-projection.md
What generate_graph_projection does on Mcpg
AI agents invoke generate_graph_projection to trigger actions in Mcpg. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why generate_graph_projection is rated High
The tool name suggests generating a graph projection, which likely involves executing a database operation to create or compute a graph structure. Given the server context includes analytical and policy tools, this likely runs a computation/transformation. Empty description lowers confidence significantly.
From the tool's definition Tool name 'generate_graph_projection' and server context (PostgreSQL MCP server with analytical tools). Description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs generate_graph_projection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_graph_projection, this is the rule to start with:
generate_graph_projection stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every generate_graph_projection call is checked against it from then on.
Questions about generate_graph_projection
generate_graph_projection is a execute tool on the Mcpg MCP server. It is categorised as a Execute tool in the Mcpg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcpg MCP server in PolicyLayer and add a rule for generate_graph_projection: 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 Mcpg. Nothing to install.
generate_graph_projection is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the generate_graph_projection 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 generate_graph_projection. 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.
generate_graph_projection is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue