Calculate graph metrics like diameter, density, clustering coefficient
AI agents call graph_calculate_metrics to retrieve information from Engineering MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and computes statistical properties of process engineering diagrams. It has no side effects: it does not create, modify, delete, or execute external operations. It falls squarely into the Read category as a data analysis/retrieval function. Severity is low because misuse would only expose diagram structure properties, not enable harmful modification or execution.
From the tool's definition Tool name and description explicitly indicate 'Calculate graph metrics' — a query operation that analyzes properties (diameter, density, clustering coefficient) of existing diagrams without modifying or deleting them.
Documented attack patterns abuse exactly the kind of access graph_calculate_metrics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Engineering MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for graph_calculate_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"graph_calculate_metrics": {}
}
}graph_calculate_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Calculate graph metrics like diameter, density, clustering coefficient. It is categorised as a Read tool in the Engineering MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Engineering MCP Server MCP server in PolicyLayer and add a rule for graph_calculate_metrics: 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 Engineering MCP Server. Nothing to install.
graph_calculate_metrics 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 graph_calculate_metrics 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 graph_calculate_metrics. 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.
graph_calculate_metrics is provided by the Engineering MCP Server MCP server (puran-water/dexpi-sfiles-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Engineering MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
72 Engineering MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.