Query data generated by a running Sage job
AI agents call query_job_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 performs a query operation to retrieve data from an existing job. The verb 'query' combined with 'data generated by' indicates read-only access to job outputs. No creation, modification, deletion, code execution, or financial action is implied. The tool has minimal blast radius if misused—worst case is unauthorized information disclosure of job data.
From the tool's definition Tool name 'query_job_data' and description 'Query data generated by a running Sage job' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Query data generated by a running Sage job. 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 query_job_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.
query_job_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 query_job_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 query_job_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.
query_job_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 →