AI agents use initialize-project-standard to create or update resources in Feuse — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Feuse environment.
This tool analyzes a user-specified project and generates/writes global project rule files for AI coding assistants (Copilot and Cursor). It creates new configuration artifacts, which is a Write operation. Misuse could inject malicious rules into development environments, warranting medium severity.
From the tool's definition 生成Copilot 和 cursor对应的全局项目规则 (generates global project rules for Copilot and Cursor)
Documented attack patterns abuse exactly the kind of access initialize-project-standard gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Feuse, and nothing reaches the server without passing your rules. This is the rule we recommend for initialize-project-standard:
{
"version": "1",
"default": "deny",
"tools": {
"initialize-project-standard": {
"limits": [
{
"counter": "initialize-project-standard_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}initialize-project-standard 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.
针对用户指定项目进行分析，生成Copilot 和 cursor对应的全局项目规则. It is categorised as a Write tool in the Feuse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Feuse MCP server in PolicyLayer and add a rule for initialize-project-standard: 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 Feuse. Nothing to install.
initialize-project-standard 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 initialize-project-standard 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 initialize-project-standard. 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.
initialize-project-standard is provided by the Feuse MCP server (panzer-jack/feuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Feuse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Feuse tools catalogued and risk-classified — across an index of 42,500+ MCP servers.