AI agents invoke setup_fpc to trigger actions in Claude Pascal 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.
The name 'setup_fpc' likely refers to setting up Free Pascal Compiler (FPC) on the system, which would involve executing installation or configuration operations. Given the server's context of compiling and running Pascal applications, this tool likely triggers system-level setup actions.
From the tool's definition Tool name 'setup_fpc' on a server that 'compiles, runs, and interacts with Pascal/Delphi desktop applications'; description is empty.
Documented attack patterns abuse exactly the kind of access setup_fpc gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Pascal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for setup_fpc:
{
"version": "1",
"default": "deny",
"tools": {
"setup_fpc": {
"limits": [
{
"counter": "setup_fpc_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}setup_fpc stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
setup_fpc. It is categorised as a Execute tool in the Claude Pascal MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Pascal MCP Server MCP server in PolicyLayer and add a rule for setup_fpc: 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 Claude Pascal MCP Server. Nothing to install.
setup_fpc 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 setup_fpc 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 setup_fpc. 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.
setup_fpc is provided by the Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Pascal MCP 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.
53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.