roll_dice

THE RISK

Low Risk

Why roll_dice needs a policy

Rolling a die is a local computation that generates a random number. It does not read, write, execute, destroy, or involve financial operations. It is a self-contained utility function with no meaningful blast radius.

From the tool's definition 'Roll an N-sided die' - this is a pure random number generation utility with no side effects, data access, or external operations

Documented attack patterns abuse exactly the kind of access roll_dice gives an agent:

POLICY

How to control roll_dice

PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for roll_dice:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "roll_dice": {
      "limits": [
        {
          "counter": "roll_dice_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

roll_dice gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register VaultAssist — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More VaultAssist tools

Destructive batch_delete_gmail_emails Delete multiple emails at once Destructive clear_completed_tasks Clear all completed tasks from a task list. The tasks will be marked as hidden Destructive delete_event Delete an event from a Google Calendar Destructive delete_gmail_email Delete an email by its message ID Destructive delete_gmail_label Delete a Gmail label Destructive delete_task Delete a task from a task list Destructive delete_task_list Delete a task list. Note: This will also delete all tasks in the list Destructive memory_delete_entities Delete and forget multiple entities and their associated relationships from the user

All 79 VaultAssist tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about roll_dice

What does the roll_dice tool do? +

Roll an N-sided die. It is categorised as a Other tool in the VaultAssist MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on roll_dice? +

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

What risk level is roll_dice? +

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

Can I rate-limit roll_dice? +

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

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

roll_dice is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every VaultAssist tool call.

Start from VaultAssist, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →