Create a new PriceAPI job for data collection. Args: source (str): Data source (amazon, ebay, google_shopping, etc.) country (str): Country code (us, uk, de, etc.) topic (str): Search topic or product identifier key (str): Search key or ASIN max_pages (int): Maximum pages to scrape (default: 1) t...
Risk signalsHandles credentials or secrets (token)
Part of the Priceapi server.
Free to start. No card required.
AI agents use create_job to create or modify resources in Priceapi. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_job repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Priceapi.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"create_job": {
"limits": [
{
"counter": "create_job_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} See the full Priceapi policy for all 6 tools.
These attack patterns abuse exactly the kind of access create_job gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Create a new PriceAPI job for data collection. Args: source (str): Data source (amazon, ebay, google_shopping, etc.) country (str): Country code (us, uk, de, etc.) topic (str): Search topic or product identifier key (str): Search key or ASIN max_pages (int): Maximum pages to scrape (default: 1) token (str | None): Optional PriceAPI token. If not provided, falls back to URL parameters or PRICEAPI_TOKEN environment variable. Returns: dict: Job creation result. It is categorised as a Write tool in the Priceapi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Priceapi MCP server in PolicyLayer and add a rule for create_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 Priceapi. Nothing to install.
create_job is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_job 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.