High Risk →

compress_pdf

Run OCR, recompose, and create a stored PDF job

Risk signalsProcesses PDFs and stores results

Part of the Optical Context MCP server.

compress_pdf can trigger actions in Optical Context MCP, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE OPTICAL CONTEXT MCP →

Free to start. No card required.

AI agents invoke compress_pdf to trigger processes or run actions in Optical Context MCP. 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.

compress_pdf 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "compress_pdf": {
      "limits": [
        {
          "counter": "compress_pdf_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Optical Context MCP policy for all 3 tools.

Get this rule live on your own Optical Context MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OPTICAL CONTEXT MCP →

These attack patterns abuse exactly the kind of access compress_pdf 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 compress_pdf only ever does what you allow.

SECURE OPTICAL CONTEXT MCP →

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

What does the compress_pdf tool do? +

Run OCR, recompose, and create a stored PDF job. It is categorised as a Execute tool in the Optical Context MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on compress_pdf? +

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

What risk level is compress_pdf? +

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

Can I rate-limit compress_pdf? +

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

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

compress_pdf is provided by the Optical Context MCP server (pypi:optical-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Optical Context MCP tool call.

Deterministic rules across all 3 Optical Context MCP 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.