Stop the running TensorBoard process.
AI agents invoke stop_tensorboard_tool to trigger actions in Qiskit Gym MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Stopping a TensorBoard process is an execute action that triggers external process management operations. While not destructive (TensorBoard can be restarted), it disrupts monitoring and training visibility. Misuse could halt observability during active training sessions, impacting the reinforcement learning workflow.
From the tool's definition Tool description: 'Stop the running TensorBoard process.' The tool executes a process termination command targeting the TensorBoard service.
Attacks that exploit this kind of access
Stop the running TensorBoard process. It is categorised as a Execute tool in the Qiskit Gym MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qiskit Gym MCP Server MCP server in PolicyLayer and add a rule for stop_tensorboard_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 Gym MCP Server. Nothing to install.
stop_tensorboard_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_tensorboard_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 stop_tensorboard_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.
stop_tensorboard_tool is provided by the Qiskit Gym MCP Server MCP server (qiskit-gym-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 →