Get recent image data from Sage nodes. Supports filtering by node and plugin pattern.
AI agents call get_image_data to retrieve information from Sage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries image data from distributed sensor nodes without modifying, deleting, or executing operations. It is a straightforward data retrieval function with support for filtering parameters (node and plugin pattern). There are no side effects or irreversible actions.
From the tool's definition Tool description states 'Get recent image data from Sage nodes' with filtering capabilities. The verb 'Get' and the read-only nature of retrieving existing sensor/image data indicates no data modification, deletion, or code execution.
Attacks that exploit this kind of access
Get recent image data from Sage nodes. Supports filtering by node and plugin pattern. It is categorised as a Read tool in the Sage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP Server MCP server in PolicyLayer and add a rule for get_image_data: 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 Sage MCP Server. Nothing to install.
get_image_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_image_data 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 get_image_data. 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.
get_image_data is provided by the Sage MCP Server MCP server (waggle-sensor/sage-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 →