Get, set or delete project structure in configuration
AI agents use project_structure to create or update resources in MCP Project Standards Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Project Standards Server environment.
The tool spans Read (get), Write (set), and Destructive (delete) operations. Per the rules, the most severe applicable category is chosen. 'Delete' on project structure configuration could be destructive, but project configuration changes are typically reversible (can be re-set), so Write is the most appropriate category. However, deleting project structure config could cause significant misconfiguration.
From the tool's definition 'Get, set or delete project structure in configuration' — the tool supports write ('set') and destructive ('delete') operations on project configuration
Documented attack patterns abuse exactly the kind of access project_structure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Project Standards Server, and nothing reaches the server without passing your rules. This is the rule we recommend for project_structure:
{
"version": "1",
"default": "deny",
"tools": {
"project_structure": {
"limits": [
{
"counter": "project_structure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} project_structure stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get, set or delete project structure in configuration. It is categorised as a Write tool in the MCP Project Standards Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Project Standards Server MCP server in PolicyLayer and add a rule for 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 MCP Project Standards Server. Nothing to install.
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 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 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.
project_structure is provided by the MCP Project Standards Server MCP server (liliangshan/mcp-server-project-standards). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Project Standards Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 MCP Project Standards Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.