Run classifier training commands on a remote host via SSH
AI agents invoke trainClassifier to trigger actions in Infer 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 code/commands on remote systems via SSH, which is characteristic of the Execute category. The blast radius is high because SSH command execution can have significant side effects depending on what commands are run—training could consume resources, modify system state, or trigger unintended operations.
From the tool's definition Tool description states 'Run classifier training commands on a remote host via SSH'. The name 'trainClassifier' combined with 'remote host via SSH' indicates execution of arbitrary commands on external systems.
Attacks that exploit this kind of access
Run classifier training commands on a remote host via SSH. It is categorised as a Execute tool in the Infer MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Infer MCP Server MCP server in PolicyLayer and add a rule for trainClassifier: 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 Infer MCP Server. Nothing to install.
trainClassifier 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 trainClassifier 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 trainClassifier. 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.
trainClassifier is provided by the Infer MCP Server MCP server (jackyxhb/infermcpserver). 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 →