random_number | PolicyLayer

WHAT IT DOES

What random_number does on Simple MCP Server with Streamable HTTP Example

AI agents invoke random_number to trigger actions in Simple MCP Server with Streamable HTTP Example. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why random_number needs a policy

This tool generates a random number, which involves executing a computation rather than simply reading stored data or writing persistent state. However, it has no side effects on external systems, data, or resources — the blast radius of misuse is essentially negligible.

From the tool's definition Generate a random integer between min_val and max_val (inclusive)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

random_number Rate-limited

random_number stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "random_number": {
      "limits": [
        {
          "counter": "random_number_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Simple MCP Server with Streamable HTTP Example, so you can run agents against it safely.

FAQ

Questions about random_number

What does the random_number tool do? +

Generate a random integer between min_val and max_val (inclusive). It is categorised as a Execute tool in the Simple MCP Server with Streamable HTTP Example MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on random_number? +

Register the Simple MCP Server with Streamable HTTP Example MCP server in PolicyLayer and add a rule for random_number: 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 Simple MCP Server with Streamable HTTP Example. Nothing to install.

What risk level is random_number? +

random_number is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit random_number? +

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

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

random_number is provided by the Simple MCP Server with Streamable HTTP Example MCP server (jonigl/mcp-server-with-streamable-http-example). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.