Lancer un scan de la bibliothèque Kodi
AI agents invoke scan_library 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 triggers an external operation on the Kodi media center — a library scan — which causes Kodi to actively traverse file system paths, index media files, and update its database. It is not a simple read (it modifies the library state) nor purely destructive, but it executes an external process with side effects. Misuse could cause performance issues or unintended library changes.
From the tool's definition Lancer un scan de la bibliothèque Kodi (Launch a scan of the Kodi library)
Attacks that exploit this kind of access
Lancer un scan de la bibliothèque 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 scan_library: 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.
scan_library 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 scan_library 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 scan_library. 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.
scan_library 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 →