Predictionguard

41 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

4 can modify or destroy data
37 read-only
41 tools total

4 Predictionguard tools can modify or destroy data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE PREDICTIONGUARD →

Free to start. No card required.

Read (37) Write / Execute (3) Destructive / Financial (1)
6,339 tokens of tool definitions, loaded on every request
3.2% of a 200k context window
549 heaviest tool: pg_sar_report

Destructive tools (pg_whale_remove) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (pg_wallet_entity_resolve, pg_whale_add) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (pg_market_volume_profile) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

Deny destructive operations
{
  "pg_whale_remove": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "pg_wallet_entity_resolve": {
    "limits": [
      {
        "counter": "pg_wallet_entity_resolve_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "pg_adverse_media_entity": {
    "limits": [
      {
        "counter": "pg_adverse_media_entity_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Get this policy live on your own Predictionguard server in minutes. Tune the limits to your setup; PolicyLayer enforces it on every call.

ENFORCE ON MY PREDICTIONGUARD →
Can an AI agent delete data through the Predictionguard MCP server? +

Yes. The Predictionguard server exposes 1 destructive tools including pg_whale_remove. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Predictionguard? +

The Predictionguard server has 2 write tools including pg_wallet_entity_resolve, pg_whale_add. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Predictionguard.

How many tools does the Predictionguard MCP server expose? +

41 tools across 4 categories: Destructive, Execute, Read, Write. 37 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on Predictionguard? +

Register the Predictionguard MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

Enforce policy on every Predictionguard tool call.

Deterministic rules across all 41 Predictionguard 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.