Star Wars

15 tools. 1 can modify or destroy data without limits.

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

Last updated:

1 can modify or destroy data
14 read-only
15 tools total
Read (14) Write / Execute (0) Destructive / Financial (1)

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

Deny destructive operations
clear_cache:
  rules:
    - action: deny

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

Cap read operations
get_cache_stats:
  rules:
    - rate_limit: 60/minute

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

Can an AI agent delete data through the Star Wars MCP server? +

Yes. The Star Wars server exposes 1 destructive tools including clear_cache. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How many tools does the Star Wars MCP server expose? +

15 tools across 2 categories: Destructive, Read. 14 are read-only. 1 can modify, create, or delete data.

How do I add Intercept to my Star Wars setup? +

One line change. Instead of running the Star Wars server directly, prefix it with Intercept: intercept -c shadowsethcpu-mcp-starwars.yaml -- npx -y @ShadowSethcpu/mcp-starwars. Download a pre-built policy from policylayer.com/policies/shadowsethcpu-mcp-starwars and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.