Toggle play/pause sur le player actif de Kodi
AI agents invoke player_play_pause to trigger actions in Kodi 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.
This tool controls playback state of an external media player application. It executes an action (toggling play/pause) on a running Kodi instance. While reversible, it is an external operation execution rather than a data read or write. Severity is low as misuse only affects media playback with no data loss or financial risk.
From the tool's definition 'Toggle play/pause sur le player actif de Kodi' — triggers an external operation (play/pause toggle) on an active Kodi media player
Attacks that exploit this kind of access
Toggle play/pause sur le player actif de Kodi. It is categorised as a Execute tool in the Kodi MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kodi MCP Server MCP server in PolicyLayer and add a rule for player_play_pause: 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 Kodi MCP Server. Nothing to install.
player_play_pause 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 player_play_pause 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 player_play_pause. 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.
player_play_pause is provided by the Kodi MCP Server MCP server (laheud/kodi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →