AI agents call export_design_md 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 returns document content as markdown text. It reads existing files or extracts content from a document without modifying or deleting anything, making it a pure read operation with minimal blast radius.
From the tool's definition Export the design.md as markdown text... auto-extracts from document content
Attacks that exploit this kind of access
Export the design.md as markdown text. If no design.md exists, auto-extracts from document content. 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 export_design_md: 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.
export_design_md 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 export_design_md 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 export_design_md. 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.
export_design_md 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 →