Create a new tracked project. Requires
AI agents use create_project to create or update resources in SurfRank MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SurfRank MCP Server environment.
The tool creates new data (a project resource) in a reversible manner. Users can delete projects afterward (as evidenced by the sibling tool 'delete_project'), making this a Write operation rather than Destructive. The severity is medium because creating projects could consume platform resources or quota, but the action is not irreversible and has limited blast radius if misused by an AI agent.
From the tool's definition Tool name is 'create_project' and description states 'Create a new tracked project.' This creates a new resource in the SurfRank analytics platform without destructive consequences.
Attacks that exploit this kind of access
Create a new tracked project. Requires. It is categorised as a Write tool in the SurfRank MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SurfRank MCP Server MCP server in PolicyLayer and add a rule for create_project: 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 SurfRank MCP Server. Nothing to install.
create_project 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_project 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_project. 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_project is provided by the SurfRank MCP Server MCP server (surfrankai/mcp-server). 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 →