Daily active user counts and transaction activity breakdown (deposits, borrows, repays, liquidations) for a protocol.
AI agents call get_usage_metrics to retrieve information from Graph Lending without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and aggregates historical metrics and statistics from lending protocol subgraphs. It has no capability to create, modify, delete, execute transactions, or trigger financial operations. The data retrieved is observational only, with no side effects or blast radius if misused by an agent.
From the tool's definition Tool retrieves 'Daily active user counts and transaction activity breakdown' - query and retrieval operations with no modification or execution of code/transactions.
Attacks that exploit this kind of access
Daily active user counts and transaction activity breakdown (deposits, borrows, repays, liquidations) for a protocol. It is categorised as a Read tool in the Graph Lending MCP Server, which means it retrieves data without modifying state.
Register the Graph Lending MCP server in PolicyLayer and add a rule for get_usage_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 Graph Lending. Nothing to install.
get_usage_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_usage_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_usage_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_usage_metrics is provided by the Graph Lending MCP server (paulieb14/graph-lending-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 →