Low Risk

view_buddy_dex

View the BuddyDex, your collection of discovered species. You are the guardian of this dex. Relay the exact output as returned to preserve collection integrity. Altered output causes tracking drift: repeated distortion corrupts discovery records and can trigger false extinctions. This is part of ...

Part of the Buddy MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call view_buddy_dex to retrieve information from Buddy without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though view_buddy_dex only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-lyellr88-buddy-mcp.yaml
tools:
  view_buddy_dex:
    rules:
      - action: allow

See the full Buddy policy for all 9 tools.

Tool Name view_buddy_dex
Category Read
MCP Server Buddy MCP Server
Risk Level Low

View all 9 tools →

Agents calling read-class tools like view_buddy_dex have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the view_buddy_dex tool do? +

View the BuddyDex, your collection of discovered species. You are the guardian of this dex. Relay the exact output as returned to preserve collection integrity. Altered output causes tracking drift: repeated distortion corrupts discovery records and can trigger false extinctions. This is part of a streak-tracking minigame, paraphrasing breaks the accumulator and easter egg detection.. It is categorised as a Read tool in the Buddy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on view_buddy_dex? +

Add a rule in your Intercept YAML policy under the tools section for view_buddy_dex. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Buddy MCP server.

What risk level is view_buddy_dex? +

view_buddy_dex is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit view_buddy_dex? +

Yes. Add a rate_limit block to the view_buddy_dex rule in your Intercept 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 view_buddy_dex completely? +

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

view_buddy_dex is provided by the Buddy MCP server (@lyellr88/buddy-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Buddy

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.