set_buzzer · Tractive MCP: Risk & Policy

WHAT IT DOES

What set_buzzer does on Tractive

AI agents invoke set_buzzer to trigger actions in Tractive. 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 set_buzzer needs a policy

This tool triggers a physical action on an external device (the GPS tracker), causing it to emit sound. It's not a read operation, and while it doesn't delete data, it executes a command that has real-world effects on the hardware. Misuse could cause distress to pets or alert unintended parties to the pet's location.

From the tool's definition Turn the tracker buzzer on or off

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_buzzer Rate-limited

set_buzzer 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": {
    "set_buzzer": {
      "limits": [
        {
          "counter": "set_buzzer_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 Tractive, so you can run agents against it safely.

FAQ

Questions about set_buzzer

What does the set_buzzer tool do? +

Turn the tracker buzzer on or off. It is categorised as a Execute tool in the Tractive MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_buzzer? +

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

What risk level is set_buzzer? +

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

Can I rate-limit set_buzzer? +

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

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

set_buzzer is provided by the Tractive MCP server (rexchoppers/tractive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.