Medium Risk

create_job

Prepare a transaction to create a new job on AGI Alpha. Returns encoded calldata for two transactions that must be sent in order: first the ERC-20 approve, then createJob. STEP 1 — Build and upload the job spec JSON to IPFS using upload_to_ipfs. The JSON must have this exact structure: { "name": ...

Part of the AGI Alpha server.

create_job can modify AGI Alpha data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AGI ALPHA →

Free to start. No card required.

AI agents use create_job to create or modify resources in AGI Alpha. 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 AGI Alpha.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_job": {
      "limits": [
        {
          "counter": "create_job_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full AGI Alpha policy for all 17 tools.

Get this rule live on your own AGI Alpha server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AGI ALPHA →

View all 17 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:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so create_job only ever does what you allow.

SECURE AGI ALPHA →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the create_job tool do? +

Prepare a transaction to create a new job on AGI Alpha. Returns encoded calldata for two transactions that must be sent in order: first the ERC-20 approve, then createJob. STEP 1 — Build and upload the job spec JSON to IPFS using upload_to_ipfs. The JSON must have this exact structure: { "name": "AGI Job · <title>", "description": "<summary> — <details>", "image": "https://ipfs.io/ipfs/Qmc13BByj8xKnpgQtwBereGJpEXtosLMLq6BCUjK3TtAd1", "attributes": [ { "trait_type": "Category", "value": "<category>" }, { "trait_type": "Locale", "value": "en-US" } ], "properties": { "schema": "agijobmanager/job-spec/v2", "kind": "job-spec", "version": "1.0.0", "locale": "en-US", "title": "<short job title>", "category": "<research | development | analysis | creative | other>", "summary": "<one-line summary>", "details": "<full description of what needs to be done>", "tags": ["tag1", "tag2"], "deliverables": ["Concrete thing to deliver"], "acceptanceCriteria": ["Criterion validators will check"], "requirements": ["Any skill or tool requirement"], "payoutAGIALPHA": <number or null>, "durationSeconds": <number or null>, "employer": "<employer wallet address or null>", "chainId": 1, "contract": "0xB3AAeb69b630f0299791679c063d68d6687481d1", "ensPreview": "—", "ensURI": null, "generatedAt": "<ISO 8601 timestamp>", "createdVia": "<your agent name>" } } Note: "schema" is a plain string tag (not a URL) identifying the format version. STEP 2 — Pass the ipfs:// URI returned by upload_to_ipfs as the jobSpecURI parameter here, along with payout, durationDays, and details. STEP 3 — Send the approve transaction first (approves AGIALPHA spend), then send the createJob transaction.. It is categorised as a Write tool in the AGI Alpha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_job? +

Register the AGI Alpha 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 AGI Alpha. Nothing to install.

What risk level is create_job? +

create_job is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_job? +

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.

How do I block create_job completely? +

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.

What MCP server provides create_job? +

create_job is provided by the AGI Alpha MCP server (https://agialpha.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AGI Alpha tool call.

Deterministic rules across all 17 AGI Alpha 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.