set_target_model
AI agents use set_target_model to create or update resources in SensorMCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SensorMCP Server environment.
The tool appears to set or update a target model parameter, which constitutes reversible data modification. Without explicit documentation, confidence is moderate. Classified as Write rather than Execute because it appears to be configuration-setting rather than triggering model training or external operations. Not Destructive since model configuration changes are typically reversible.
From the tool's definition Tool name 'set_target_model' with empty description. Based on sibling tools 'set_base_model' and 'train_model' context, this likely modifies model configuration state.
Attacks that exploit this kind of access
set_target_model. It is categorised as a Write tool in the SensorMCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SensorMCP Server MCP server in PolicyLayer and add a rule for set_target_model: 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 SensorMCP Server. Nothing to install.
set_target_model is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_target_model 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 set_target_model. 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.
set_target_model is provided by the SensorMCP Server MCP server (sensormcp/sensor-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 →