Get usage statistics and quota information for the active instance.
AI agents call usage_info_tool to retrieve information from Qiskit Documentation 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 (usage statistics and quota details) about an active computational instance. No data is created, modified, deleted, or financial operations are performed. The operation is purely observational and has no side effects on the system state, making it a straightforward Read category risk.
From the tool's definition Tool name 'usage_info_tool' and description 'Get usage statistics and quota information for the active instance' indicate retrieval of read-only metrics and status information.
Attacks that exploit this kind of access
Get usage statistics and quota information for the active instance. It is categorised as a Read tool in the Qiskit Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qiskit Documentation MCP Server MCP server in PolicyLayer and add a rule for usage_info_tool: 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 Qiskit Documentation MCP Server. Nothing to install.
usage_info_tool 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 usage_info_tool 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 usage_info_tool. 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.
usage_info_tool is provided by the Qiskit Documentation MCP Server MCP server (pypi:qiskit-mcp-server). 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 →