call_service

Call a Home Assistant service, for example domain='light', service='turn_on'.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/call-service.md

WHAT IT DOES

What call_service does on Mcp Control Plane

AI agents invoke call_service to trigger actions in Mcp Control Plane. 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.

RISK

Why call_service is rated High

This tool triggers external operations in Home Assistant (smart home devices, automations, etc.). While some calls are benign (turn on a light), the same interface can control locks, alarms, thermostats, or other critical home systems. The effects depend heavily on the arguments passed, and some actions (e.g., unlocking doors, disabling alarms) can have serious real-world consequences.

From the tool's definition 'Call a Home Assistant service, for example domain=\'light\', service=\'turn_on\'.'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs call_service safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For call_service, this is the rule to start with:

call_service Rate-limited

call_service 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": {
    "call_service": {
      "limits": [
        {
          "counter": "call_service_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every call_service call is checked against it from then on.

FAQ

Questions about call_service

What does the call_service tool do? +

Call a Home Assistant service, for example domain='light', service='turn_on'. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on call_service? +

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

What risk level is call_service? +

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

Can I rate-limit call_service? +

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

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

call_service is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools → High-risk tools on this server →

Across the catalogue

call_rpc on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →