run_inference
AI agents invoke run_inference to trigger actions in Roboflow 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.
This tool executes inference operations on computer vision models, which is a computational action with effects determined by the model and input data. While inference itself is typically read-only from the user's perspective, it triggers external ML model execution and could consume computational resources or return sensitive predictions depending on the model's purpose.
From the tool's definition Tool name 'run_inference' combined with server description stating it 'perform[s] inference directly from the CLI' indicates execution of model inference operations.
Attacks that exploit this kind of access
run_inference. It is categorised as a Execute tool in the Roboflow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Roboflow MCP Server MCP server in PolicyLayer and add a rule for run_inference: 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 Roboflow MCP Server. Nothing to install.
run_inference 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 run_inference 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 run_inference. 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.
run_inference is provided by the Roboflow MCP Server MCP server (nickedridge-wq/roboflow-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 →