send_custom_action · Bond MCP Server MCP: Risk & Policy

WHAT IT DOES

What send_custom_action does on Bond MCP Server

AI agents invoke send_custom_action to trigger actions in Bond MCP Server. 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 send_custom_action needs a policy

This tool sends arbitrary custom actions to Bond Bridge devices (fans, shades, lights, RF-controlled devices). Since the action is 'custom' and unspecified, it can trigger a wide range of physical device operations beyond the predefined controls available in sibling tools.

From the tool's definition 'Send a custom action to a Bond device' — executes arbitrary/custom commands on physical smart home devices

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_custom_action Rate-limited

send_custom_action 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": {
    "send_custom_action": {
      "limits": [
        {
          "counter": "send_custom_action_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 Bond MCP Server, so you can run agents against it safely.

FAQ

Questions about send_custom_action

What does the send_custom_action tool do? +

Send a custom action to a Bond device. It is categorised as a Execute tool in the Bond MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on send_custom_action? +

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

What risk level is send_custom_action? +

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

Can I rate-limit send_custom_action? +

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

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

send_custom_action is provided by the Bond MCP Server MCP server (madorn/bond-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.