AI agents call get_graph_metrics to retrieve information from Repowise without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve metrics from a dependency graph or codebase analysis layer, which is a read operation with no side effects. However, confidence is moderately reduced because the description is empty, leaving some ambiguity about exact functionality. The low severity reflects that querying graph metrics poses minimal risk to system integrity.
From the tool's definition Tool name 'get_graph_metrics' combined with server description indicating 'dependency graph' as one of five intelligence layers. The 'get_' prefix and metric-retrieval nature suggest read-only querying.
Documented attack patterns abuse exactly the kind of access get_graph_metrics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Repowise, and nothing reaches the server without passing your rules. This is the rule we recommend for get_graph_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"get_graph_metrics": {}
}
}get_graph_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.
get_graph_metrics. It is categorised as a Read tool in the Repowise MCP Server, which means it retrieves data without modifying state.
Register the Repowise MCP server in PolicyLayer and add a rule for get_graph_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 Repowise. Nothing to install.
get_graph_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 get_graph_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 get_graph_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.
get_graph_metrics is provided by the Repowise MCP server (repowise-dev/repowise). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Repowise tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Repowise tools catalogued and risk-classified — across an index of 42,500+ MCP servers.