This record as markdown: /tools/io-github-devopam-mcpg/analyze-distance-metric.md
What analyze_distance_metric does on Mcpg
AI agents call analyze_distance_metric to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why analyze_distance_metric is rated Low
The tool name indicates it performs analysis or inspection of distance metrics in the database context. Analysis tools typically query and return information without modifying state. The naming convention matches other analytical tools on the server (all prefixed with 'analyze_').
From the tool's definition Tool name 'analyze_distance_metric' suggests analysis/inspection of distance metrics; sibling tools like 'analyze_hnsw_recall', 'analyze_lock_hotspots', 'analyze_query_plan' are all read-only analytical operations.
Attacks that exploit this kind of access
The rule that runs analyze_distance_metric 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 analyze_distance_metric, this is the rule to start with:
analyze_distance_metric 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 Mcpg, apply this rule, and every analyze_distance_metric call is checked against it from then on.
Questions about analyze_distance_metric
analyze_distance_metric is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for analyze_distance_metric: 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.
analyze_distance_metric 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 analyze_distance_metric 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 analyze_distance_metric. 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.
analyze_distance_metric 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