AI agents call daisyui_get_theme_info to retrieve information from Daisyui without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns theme configuration documentation and metadata without modifying any data, executing code, or triggering external operations. It is purely informational, similar to the sibling tools daisyui_get_component and daisyui_get_examples which are documentation/reference lookups. Low severity due to complete absence of side effects or ability to cause harm.
From the tool's definition Tool retrieves theme information ('Get information about daisyUI themes, including available theme names and how to configure them'). The verb 'Get' and description indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
Get information about daisyUI themes, including available theme names and how to configure them in React. It is categorised as a Read tool in the Daisyui MCP Server, which means it retrieves data without modifying state.
Register the Daisyui MCP server in PolicyLayer and add a rule for daisyui_get_theme_info: 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 Daisyui. Nothing to install.
daisyui_get_theme_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the daisyui_get_theme_info 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 daisyui_get_theme_info. 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.
daisyui_get_theme_info is provided by the Daisyui MCP server (matracey/daisyui-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 →