Get the status and metrics of a training session.
AI agents call get_training_status_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 is a read-only operation that queries the status and metrics of a training session. No data is created, modified, deleted, or executed. The blast radius is minimal—an AI agent calling this tool can only view information already available, with no side effects or security impact.
From the tool's definition Tool name contains 'get' and description states 'Get the status and metrics of a training session' — purely retrieves information about an existing training session without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get the status and metrics of a training session. 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 get_training_status_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.
get_training_status_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 get_training_status_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 get_training_status_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.
get_training_status_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 →