phalcon_create_scaffold
AI agents use phalcon_create_scaffold to create or update resources in Phalcon MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Phalcon MCP Server environment.
This tool creates new artifacts within a Phalcon project, which is a reversible Write operation. While the description is empty, the name and context of sibling creation tools strongly indicate it generates code/structure files. It does not execute arbitrary operations (Execute), permanently delete data (Destructive), or handle money (Financial).
From the tool's definition Tool name 'phalcon_create_scaffold' combined with sibling tools that all create framework artifacts (phalcon_create_project, phalcon_create_model, phalcon_create_controller, etc.).
Attacks that exploit this kind of access
phalcon_create_scaffold. It is categorised as a Write tool in the Phalcon MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Phalcon MCP Server MCP server in PolicyLayer and add a rule for phalcon_create_scaffold: 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 Phalcon MCP Server. Nothing to install.
phalcon_create_scaffold 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 phalcon_create_scaffold 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 phalcon_create_scaffold. 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.
phalcon_create_scaffold is provided by the Phalcon MCP Server MCP server (xindong888999/phalcon-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 →