beeper_send_message · Garza Home MCP: Risk & Policy

WHAT IT DOES

What beeper_send_message does on Garza Home MCP

AI agents use beeper_send_message to create or update resources in Garza Home MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Garza Home MCP environment.

WHY IT NEEDS A POLICY

Why beeper_send_message needs a policy

Sending a message creates new data (the message itself) that can be retrieved, edited, or deleted by the user, making it reversible. While it affects communication and could be misused to send spam or impersonate the user, it lacks the irreversibility of destructive operations, the real-world impact of financial transactions, or the systemic risk of arbitrary code execution.

From the tool's definition Tool name 'beeper_send_message' and description 'Send a message' indicate creation of new message data in the Beeper unified messaging system. This is a write operation that creates reversible content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

beeper_send_message Rate-limited

beeper_send_message stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "beeper_send_message": {
      "limits": [
        {
          "counter": "beeper_send_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Garza Home MCP, so you can run agents against it safely.

FAQ

Questions about beeper_send_message

What does the beeper_send_message tool do? +

Send a message. It is categorised as a Write tool in the Garza Home MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on beeper_send_message? +

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

What risk level is beeper_send_message? +

beeper_send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit beeper_send_message? +

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

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

beeper_send_message is provided by the Garza Home MCP server (itsablabla/garza-home-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.