Compile the typespec project in the given directory.
AI agents invoke compile to trigger actions in TypeSpec 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.
Compilation is an Execute action because it runs code (a compiler) with side effects (generates output files, modifies the filesystem, may invoke external tools or scripts). While not destructive by design, a malicious agent could abuse this to generate malicious code, corrupt project state, or consume resources.
From the tool's definition Tool performs 'compile' action on a TypeSpec project, which executes a build process with external dependencies and code generation effects.
Documented attack patterns abuse exactly the kind of access compile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TypeSpec MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for compile:
{
"version": "1",
"default": "deny",
"tools": {
"compile": {
"limits": [
{
"counter": "compile_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}compile 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.
Compile the typespec project in the given directory. It is categorised as a Execute tool in the TypeSpec MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TypeSpec MCP Server MCP server in PolicyLayer and add a rule for compile: 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 TypeSpec MCP Server. Nothing to install.
compile 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 compile 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 compile. 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.
compile is provided by the TypeSpec MCP Server MCP server (microsoft/typespec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TypeSpec 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.
28 TypeSpec MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.