control_shades · Bond MCP Server MCP: Risk & Policy

WHAT IT DOES

What control_shades does on Bond MCP Server

AI agents invoke control_shades 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 control_shades needs a policy

Based on the server context, this tool likely sends commands to control motorized shades (open/close/position), which constitutes triggering external operations on physical devices. The sibling tools confirm the pattern of device control actions. Empty description lowers confidence, but the name and context strongly suggest Execute-level physical device actuation.

From the tool's definition Tool name 'control_shades' on a server that 'controls Bond Bridge smart home devices including motorized shades'. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

control_shades Rate-limited

control_shades 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": {
    "control_shades": {
      "limits": [
        {
          "counter": "control_shades_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 control_shades

What does the control_shades tool do? +

control_shades. 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 control_shades? +

Register the Bond MCP Server MCP server in PolicyLayer and add a rule for control_shades: 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 control_shades? +

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

Can I rate-limit control_shades? +

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

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

control_shades 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.