Check the current status of a job. Returns status, deliverable if submitted, and timing information.
AI agents call meshledger_check_job to retrieve information from Meshledger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation: it queries and returns job status, deliverable details, and timing information. There are no side effects, no state changes, no irreversible actions, and no financial movements. The operation is purely informational and safe for an AI agent to invoke without risk of data loss or unintended consequences.
From the tool's definition Tool name 'check_job' and description 'Check the current status of a job. Returns status, deliverable if submitted, and timing information.' indicate a query operation that retrieves data about an existing job without modifying it.
Attacks that exploit this kind of access
Check the current status of a job. Returns status, deliverable if submitted, and timing information. It is categorised as a Read tool in the Meshledger MCP Server, which means it retrieves data without modifying state.
Register the Meshledger MCP server in PolicyLayer and add a rule for meshledger_check_job: 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 Meshledger. Nothing to install.
meshledger_check_job 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 meshledger_check_job 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 meshledger_check_job. 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.
meshledger_check_job is provided by the Meshledger MCP server (meshledger/meshledger). 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 →