extract_async · Extracto MCP: Risk & Policy

WHAT IT DOES

What extract_async does on Extracto

AI agents invoke extract_async to trigger actions in Extracto. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why extract_async needs a policy

This tool triggers an external operation (an asynchronous job) that fetches and processes a remote URL, potentially interacting with anti-bot-protected pages. It goes beyond simple reads by executing background jobs with side effects on external systems. The blast radius is medium as misuse could involve scraping protected pages or triggering unintended network activity.

From the tool's definition Submit an asynchronous extraction job for a heavy, slow, or anti-bot-protected page

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

extract_async Rate-limited

extract_async stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "extract_async": {
      "limits": [
        {
          "counter": "extract_async_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Extracto, so you can run agents against it safely.

FAQ

Questions about extract_async

What does the extract_async tool do? +

Submit an asynchronous extraction job for a heavy, slow, or anti-bot-protected page. It is categorised as a Execute tool in the Extracto MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on extract_async? +

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

What risk level is extract_async? +

extract_async is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit extract_async? +

Yes. Add a rate_limit block to the extract_async 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 extract_async completely? +

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

extract_async is provided by the Extracto MCP server (massanaroger/extracto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.