Run the base model over RAW_IMAGES_DIR and save labels.
AI agents invoke label_images to trigger actions in SensorMCP 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 an ML model pipeline over images and saves the resulting label files. It involves both running external model inference (Execute) and writing output files (Write). Since it triggers an external computation process whose effects depend on the base model and image inputs, Execute is the most appropriate category, ranked above Write.
From the tool's definition 'Run the base model over RAW_IMAGES_DIR and save labels' — triggers execution of a foundation model (GroundedSAM) over a directory of images and writes output label files
Attacks that exploit this kind of access
Run the base model over RAW_IMAGES_DIR and save labels. It is categorised as a Execute tool in the SensorMCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SensorMCP Server MCP server in PolicyLayer and add a rule for label_images: 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.
label_images 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 label_images 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 label_images. 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.
label_images 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 →