create_project_structure
AI agents use create_project_structure to create or update resources in Project Creator MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Creator MCP environment.
The description is empty, so classification relies on the tool name and server context. 'create_project_structure' strongly implies creating directories and files on the filesystem, which is a Write operation. Sibling tools like 'create_directory', 'create_file', and 'create_project_from_template' confirm the server's write-heavy nature.
From the tool's definition Tool name 'create_project_structure' and server context 'project scaffolding with file system operations, template management, and command execution capabilities'
Attacks that exploit this kind of access
create_project_structure. It is categorised as a Write tool in the Project Creator MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Project Creator MCP server in PolicyLayer and add a rule for create_project_structure: 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 Project Creator MCP. Nothing to install.
create_project_structure 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_structure 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_structure. 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_structure is provided by the Project Creator MCP server (jackalterman/project-creator-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 →