Create a page-type feature spec linked to a keyword cluster. The spec carries the content strategy (outline, goals, voice, inspiration); keyword data is resolved dynamically from the cluster at read time. Use this after creating keyword clusters to generate actionable content briefs. Each cluster...
AI agents use create_content_spec to create or update resources in Rampify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rampify MCP Server environment.
This tool creates structured content specifications and briefs, which are reversible data artifacts that persist in the system. It does not execute code, delete data, or move money. It generates metadata and instructions for content optimization but does not directly execute those instructions or modify production content.
From the tool's definition create_content_spec 'Create a page-type feature spec linked to a keyword cluster'; 'auto-creates tasks: write content, optimize for keywords, add schema/meta'; 'response includes spec_id' — tool creates and stores new content specifications/briefs.
Attacks that exploit this kind of access
Create a page-type feature spec linked to a keyword cluster. The spec carries the content strategy (outline, goals, voice, inspiration); keyword data is resolved dynamically from the cluster at read time. Use this after creating keyword clusters to generate actionable content briefs. Each cluster maps to one page — the spec tells an AI agent exactly what to build. The spec auto-creates tasks: write content, optimize for keywords, add schema/meta. The response includes the spec_id. Use get_feature_spec with that ID to retrieve the full spec with live keyword data, volumes, and GSC performance. It is categorised as a Write tool in the Rampify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rampify MCP Server MCP server in PolicyLayer and add a rule for create_content_spec: 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 Rampify MCP Server. Nothing to install.
create_content_spec 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 create_content_spec 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 create_content_spec. 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.
create_content_spec is provided by the Rampify MCP Server MCP server (rampify-dev/rampify-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 →