yandex_station_say_by_name
Make a Yandex media_player say text by friendly name or entity_id substring.
This record as markdown: /tools/mcp-control-plane/yandex-station-say-by-name.md
What yandex_station_say_by_name does on Mcp Control Plane
AI agents invoke yandex_station_say_by_name 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.
Why yandex_station_say_by_name is rated High
This tool causes a real-world side effect by making a Yandex Station device speak aloud. It is not a read or write operation on data, but an execution of an action on an external device. Misuse could involve broadcasting unwanted or harmful audio content in a home environment, hence medium severity.
From the tool's definition Make a Yandex media_player say text — triggers an external operation (text-to-speech output on a physical device)
Attacks that exploit this kind of access
The rule that runs yandex_station_say_by_name 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 yandex_station_say_by_name, this is the rule to start with:
yandex_station_say_by_name 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every yandex_station_say_by_name call is checked against it from then on.
Questions about yandex_station_say_by_name
Make a Yandex media_player say text by friendly name or entity_id substring. 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.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for yandex_station_say_by_name: 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.
yandex_station_say_by_name is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the yandex_station_say_by_name 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.
Set action: deny in the PolicyLayer policy for yandex_station_say_by_name. 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.
yandex_station_say_by_name 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.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue