get_usage
AI agents call get_usage to retrieve information from FineData MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_usage' indicates a read-only operation that retrieves usage information, likely about API calls, quotas, or system metrics. Without a description, confidence is moderate, but the verb 'get' strongly implies data retrieval rather than modification, execution, or destructive action. Even in the context of a scraping server, a usage metrics tool would not directly perform scraping or modify data.
From the tool's definition Tool name 'get_usage' suggests retrieval of usage metrics or statistics. The description is empty, limiting certainty. Based on naming convention, this appears to be a query/retrieval function with no side effects.
Attacks that exploit this kind of access
get_usage. It is categorised as a Read tool in the FineData MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FineData MCP Server MCP server in PolicyLayer and add a rule for get_usage: 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 FineData MCP Server. Nothing to install.
get_usage 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 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. 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 is provided by the FineData MCP Server MCP server (quality-network/finedata-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 →