Export all notes to markdown files in a directory
AI agents use export_all_notes_to_markdown to create or update resources in MCP Note-Taking Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Note-Taking Server environment.
An AI agent can call export_all_notes_to_markdown faster than any human can review — one bad instruction and it creates or modifies resources in MCP Note-Taking Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Export all notes to markdown files in a directory. It is categorised as a Write tool in the MCP Note-Taking Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Note-Taking Server MCP server in PolicyLayer and add a rule for export_all_notes_to_markdown: 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 MCP Note-Taking Server. Nothing to install.
export_all_notes_to_markdown 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 export_all_notes_to_markdown 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_all_notes_to_markdown. 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_all_notes_to_markdown is provided by the MCP Note-Taking Server MCP server (starrstack/mcp-notes). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.