AI agents use md_generate_toc to create or update resources in LuzzyTool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LuzzyTool environment.
The tool performs content generation/modification by creating a table of contents within a Markdown document. While reversible (the generated TOC can be deleted or regenerated), this is fundamentally a write operation. It does not retrieve external data (Read), execute arbitrary code (Execute), delete data (Destructive), or involve financial transactions (Financial).
From the tool's definition The tool name 'md_generate_toc' and description '【Markdown】从 Markdown 内容生成目录(Table of Contents)' indicate it generates a table of contents from Markdown content. This is a write operation that creates or modifies document structure.
Attacks that exploit this kind of access
【Markdown】从 Markdown 内容生成目录(Table of Contents)。. It is categorised as a Write tool in the LuzzyTool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LuzzyTool MCP server in PolicyLayer and add a rule for md_generate_toc: 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 LuzzyTool. Nothing to install.
md_generate_toc 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 md_generate_toc 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 md_generate_toc. 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.
md_generate_toc is provided by the LuzzyTool MCP server (luzzymeow/luzzytool). 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 →