New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

yandex_station_command

Send a native command to a Yandex.Station media_player entity.

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/yandex-station-command.md

What yandex_station_command does on Mcp Control Plane

AI agents invoke yandex_station_command 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_command is rated High

The tool sends commands to an external device (Yandex Station), which triggers external operations on the media player. This is an Execute-category action as it interacts with and controls a physical/virtual device. Misuse could cause unintended playback, volume changes, or other device actions, warranting medium severity.

From the tool's definition Send a native command to a Yandex.Station media_player entity

Questions about yandex_station_command

What does the yandex_station_command tool do? +

Send a native command to a Yandex.Station media_player entity. 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 yandex_station_command? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for yandex_station_command: 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 yandex_station_command? +

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

Can I rate-limit yandex_station_command? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Control Plane's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.