Create a PlugLayer project namespace. Project creation only requires authentication.
AI agents use create_project to create or update resources in PlugLayer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PlugLayer MCP Server environment.
The tool creates a new project namespace within the PlugLayer platform. Creation is reversible (the sibling 'delete_project' confirms projects can be deleted), and the effects are scoped to a new namespace without immediate side effects beyond resource allocation. This is a Write operation.
From the tool's definition Tool name 'create_project' and description 'Create a PlugLayer project namespace' indicate data creation. Context shows this is infrastructure-as-code with 'deploying and managing infrastructure via natural language', paired with sibling tools like…
Attacks that exploit this kind of access
Create a PlugLayer project namespace. Project creation only requires authentication. It is categorised as a Write tool in the PlugLayer MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PlugLayer 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 PlugLayer 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 PlugLayer MCP Server MCP server (pluglayer/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 →