enable_library_source
AI agents use enable_library_source to create or update resources in DM20 Protocol — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DM20 Protocol environment.
Without a description, confidence is reduced. However, 'enable' suggests toggling a setting or source state rather than executing arbitrary code (Execute), deleting data (Destructive), or merely querying (Read). In the context of a D&D campaign manager with RAG rulebook access, enabling a library source likely activates access to a rulebook PDF or knowledge base, which is a reversible configuration change.
From the tool's definition Tool name 'enable_library_source' suggests activating or enabling a data source within a library system. The empty description prevents direct confirmation, but 'enable' typically indicates a state-changing operation that modifies configuration.
Attacks that exploit this kind of access
enable_library_source. It is categorised as a Write tool in the DM20 Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DM20 Protocol MCP server in PolicyLayer and add a rule for enable_library_source: 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 DM20 Protocol. Nothing to install.
enable_library_source is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the enable_library_source 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 enable_library_source. 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.
enable_library_source is provided by the DM20 Protocol MCP server (polloinfilzato/dm20-protocol). 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 →