Régler le volume de Kodi (0-100)
AI agents invoke set_volume 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.
Setting volume is an external operation that controls a media system's hardware/software state. It's not purely reading data, nor is it writing persistent data or destructive. It executes a command against the Kodi player. Severity is low because the blast radius of misuse is minimal — worst case is volume set to 0 or 100.
From the tool's definition 'Régler le volume de Kodi (0-100)' — triggers an external operation on the Kodi media center (changing audio volume), which is a real-time system action with immediate effect on a running application.
Attacks that exploit this kind of access
Régler le volume de Kodi (0-100). 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 set_volume: 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.
set_volume 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 set_volume 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 set_volume. 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.
set_volume 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 →