Get current license and usage information.
AI agents call get_usage_info to retrieve information from KeyNeg 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 informational data about license status and usage metrics. It performs no modifications, executions, deletions, or financial transactions. The blast radius of misuse is minimal—an attacker could learn resource consumption details or license constraints, but cannot alter system state or access sensitive analytical data beyond usage statistics.
From the tool's definition Tool name 'get_usage_info' and description 'Get current license and usage information' indicate a data retrieval operation with no modification or side effects. The verb 'Get' combined with querying license and usage metrics is a read-only action.
Attacks that exploit this kind of access
Get current license and usage information. It is categorised as a Read tool in the KeyNeg MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KeyNeg MCP Server MCP server in PolicyLayer and add a rule for get_usage_info: 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 KeyNeg MCP Server. Nothing to install.
get_usage_info 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_info 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_info. 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_info is provided by the KeyNeg MCP Server MCP server (osseni94/keyneg-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 →