Stape

18 tools. 9 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated:

9 can modify or destroy data
9 read-only
18 tools total

Community server · catalogue entry verified 05/07/2026

How to control Stape ↓

What Stape exposes to your agents

Read (9) Write / Execute (7) Destructive / Financial (2)
Critical Risk

The most dangerous Stape tools

9 of Stape's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Stape

PolicyLayer is an MCP gateway — it sits between your AI agents and Stape, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default
{
  "stape_container_paddle": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

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

Prevents bulk unintended modifications from agents caught in loops.

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

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

  1. Create a free account and register Stape — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON STAPE →

Instant setup, no code required.

All 18 Stape tools

Questions about Stape

Can an AI agent move money through the Stape MCP server? +

Yes. The Stape server exposes 2 financial tools including stape_container_paddle, stape_container_subscription. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Stape? +

The Stape server has 7 write tools including stape_account, stape_container_crud, stape_container_domains. 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 Stape.

How many tools does the Stape MCP server expose? +

18 tools across 1 categories: Read. 9 are read-only. 9 can modify, create, or delete data.

How do I enforce a policy on Stape? +

Register the Stape 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.

Enforce policy on every Stape tool call.

Deterministic rules across all 18 Stape tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

18 Stape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.