AI agents call list_theme_presets to retrieve information from Pen without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates files from a directory without modifying, deleting, or executing anything. It is a read-only operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name is 'list_theme_presets' and description states 'List all .optheme preset files in a directory' — a query operation with no side effects.
Attacks that exploit this kind of access
List all .optheme preset files in a directory. It is categorised as a Read tool in the Pen MCP Server, which means it retrieves data without modifying state.
Register the Pen MCP server in PolicyLayer and add a rule for list_theme_presets: 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 Pen. Nothing to install.
list_theme_presets 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 list_theme_presets 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 list_theme_presets. 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.
list_theme_presets is provided by the Pen MCP server (@zseven-w/pen-mcp). 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 →