AI agents use generate_openspec_spec to create or update resources in Trae-OpenSpec MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Trae-OpenSpec MCP environment.
This tool creates or writes specification files, which is a reversible operation (files can be modified or deleted later). It does not execute code, delete data irreversibly, or move money. The severity is medium because malformed or malicious specifications could cause issues downstream when used by other tools like optimize_code_by_spec or deployment processes, but the tool itself only creates data artifacts.
From the tool's definition Tool name 'generate_openspec_spec' and description '根据需求生成OpenSpec规范文件' (generates OpenSpec specification files based on requirements) indicate file creation. Server description confirms it 'features tools for generating specification files'.
Documented attack patterns abuse exactly the kind of access generate_openspec_spec gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Trae-OpenSpec MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_openspec_spec:
{
"version": "1",
"default": "deny",
"tools": {
"generate_openspec_spec": {
"limits": [
{
"counter": "generate_openspec_spec_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_openspec_spec 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.
根据需求生成OpenSpec规范文件. It is categorised as a Write tool in the Trae-OpenSpec MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Trae-OpenSpec MCP server in PolicyLayer and add a rule for generate_openspec_spec: 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 Trae-OpenSpec MCP. Nothing to install.
generate_openspec_spec 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_openspec_spec 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_openspec_spec. 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_openspec_spec is provided by the Trae-OpenSpec MCP server (leon30083/trae-openspec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Trae-OpenSpec MCP, 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.
3 Trae-OpenSpec MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.