Generate project rules content based on standards. Returns content and suggested save path for user confirmation.
AI agents use generate_rules 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.
This tool creates new rule files or modifies existing ones based on project standards. While it requires user confirmation before saving (mitigating factor), the core function is generative and results in written artifacts. This is Write rather than Execute because it generates static content/configuration rather than running code with side effects.
From the tool's definition Tool generates content (rules) and suggests save paths, indicating it performs create/write operations. The description states 'Returns content and suggested save path for user confirmation,' showing intent to create or modify project files.
Documented attack patterns abuse exactly the kind of access generate_rules 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 generate_rules:
{
"version": "1",
"default": "deny",
"tools": {
"generate_rules": {
"limits": [
{
"counter": "generate_rules_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_rules 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.
Generate project rules content based on standards. Returns content and suggested save path for user confirmation. 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 generate_rules: 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.
generate_rules 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 generate_rules 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 generate_rules. 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.
generate_rules 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.