check_errand

Check an errand's status / collect its result + artifact_url.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/check-errand.md

WHAT IT DOES

What check_errand does on Gateway

AI agents call check_errand to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`job_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why check_errand is rated Low

This tool performs a read-only operation—it checks the status of an errand and retrieves its result and artifact URL. There are no side effects, no data modification, no code execution, and no destructive or financial impacts. It falls squarely into the Read category with low severity, as misuse would only expose information the agent already has access to.

From the tool's definition check_errand: Check an errand's status / collect its result + artifact_url. The tool retrieves status information and results without modifying, deleting, or executing anything. It is a pure query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_errand safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_errand, this is the rule to start with:

check_errand Allowed

check_errand is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_errand": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every check_errand call is checked against it from then on.

FAQ

Questions about check_errand

What does the check_errand tool do? +

Check an errand's status / collect its result + artifact_url. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.

What parameters does check_errand accept? +

check_errand accepts 1 parameter: job_id. Required: job_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on check_errand? +

Register the Gateway MCP server in PolicyLayer and add a rule for check_errand: 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 Gateway. Nothing to install.

What risk level is check_errand? +

check_errand is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_errand? +

Yes. Add a rate_limit block to the check_errand 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.

How do I block check_errand completely? +

Set action: deny in the PolicyLayer policy for check_errand. 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.

What MCP server provides check_errand? +

check_errand is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →