get_job_status
AI agents call get_job_status to retrieve information from Asset Aware without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves job status information, which is a non-destructive read operation. It does not create, modify, delete, or execute external operations. Given the server's asset-aware context, it likely checks the status of document processing jobs. The lack of description lowers confidence slightly, but the name strongly suggests a read-only query.
From the tool's definition Tool name 'get_job_status' indicates a query or status retrieval operation. No description provided, but the naming pattern aligns with retrieving job state without modification.
Attacks that exploit this kind of access
get_job_status. It is categorised as a Read tool in the Asset Aware MCP Server, which means it retrieves data without modifying state.
Register the Asset Aware MCP server in PolicyLayer and add a rule for get_job_status: 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 Asset Aware. Nothing to install.
get_job_status 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_job_status 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_job_status. 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_job_status is provided by the Asset Aware MCP server (u9401066/asset-aware-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 →