Wait for a job to complete and return results. Args: job_id (str): The job ID to wait for token (str | None): Optional PriceAPI token. If not provided, falls back to URL parameters or PRICEAPI_TOKEN environment variable. max_wait_time (int): Maximum time to wait in seconds (default: 300) check_in...
Risk signalsHandles credentials or secrets (token)
Part of the Priceapi server.
Free to start. No card required.
AI agents invoke wait_for_job_completion to trigger processes or run actions in Priceapi. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
wait_for_job_completion can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"wait_for_job_completion": {
"limits": [
{
"counter": "wait_for_job_completion_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Priceapi policy for all 6 tools.
These attack patterns abuse exactly the kind of access wait_for_job_completion gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Wait for a job to complete and return results. Args: job_id (str): The job ID to wait for token (str | None): Optional PriceAPI token. If not provided, falls back to URL parameters or PRICEAPI_TOKEN environment variable. max_wait_time (int): Maximum time to wait in seconds (default: 300) check_interval (int): Time between status checks in seconds (default: 10) Returns: dict: Job completion result. It is categorised as a Execute tool in the Priceapi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Priceapi MCP server in PolicyLayer and add a rule for wait_for_job_completion: 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 Priceapi. Nothing to install.
wait_for_job_completion is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wait_for_job_completion 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 wait_for_job_completion. 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.
wait_for_job_completion is provided by the Priceapi MCP server (asmaaziry19/priceapi_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Priceapi tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.