USE THIS TOOL ONLY to get text content without creating drafts or posts. Returns JSON with Pinterest and Instagram text. DOES NOT create drafts in Late API. When user asks to
AI agents call generate_content to retrieve information from Content Automation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool explicitly states it only returns generated text content (JSON with Pinterest and Instagram text) and does not create, modify, or persist any data. It is a pure read/generation operation with no side effects on external systems.
From the tool's definition 'USE THIS TOOL ONLY to get text content without creating drafts or posts' and 'DOES NOT create drafts in Late API'
Attacks that exploit this kind of access
USE THIS TOOL ONLY to get text content without creating drafts or posts. Returns JSON with Pinterest and Instagram text. DOES NOT create drafts in Late API. When user asks to. It is categorised as a Read tool in the Content Automation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Content Automation MCP Server MCP server in PolicyLayer and add a rule for generate_content: 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 Content Automation MCP Server. Nothing to install.
generate_content 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 generate_content 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_content. 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_content is provided by the Content Automation MCP Server MCP server (ysh-fe/content_automation). 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 →