Generate content for a given title.
AI agents use generate_title to create or update resources in Notemd MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notemd MCP Server environment.
This tool creates or generates new data (markdown content) based on a provided title, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or perform irreversible actions. Severity is medium because AI-generated content could introduce misinformation or spam into the knowledge base, but the changes are reversible through normal edit/delete operations.
From the tool's definition Tool description states 'Generate content for a given title' which creates new markdown content. Server description confirms 'content generation from titles' as a core capability.
Attacks that exploit this kind of access
Generate content for a given title. It is categorised as a Write tool in the Notemd MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Notemd MCP Server MCP server in PolicyLayer and add a rule for generate_title: 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 Notemd MCP Server. Nothing to install.
generate_title 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 generate_title 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 generate_title. 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.
generate_title is provided by the Notemd MCP Server MCP server (jacobinwwey/notemd-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 →