Serve the application
AI agents invoke phalcon_serve to trigger actions in Phalcon MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Serving an application launches a persistent external process (a web server), which is an execution of an external operation with real side effects (network binding, process spawning). It does not delete data or move money, but it does trigger an external operation whose effects depend on the application state and arguments.
From the tool's definition "Serve the application" — starts a web server process to run the application
Attacks that exploit this kind of access
Serve the application. It is categorised as a Execute tool in the Phalcon MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Phalcon MCP Server MCP server in PolicyLayer and add a rule for phalcon_serve: 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_serve is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the phalcon_serve 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_serve. 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_serve 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 →