run_typecheck
Run TypeScript type-checking (tsc --noEmit) for a service. Returns structured errors with file, line, column, and message. Call after writing code to verify correctness before committing.
This record as markdown: /tools/2loch-ness6-mempalace-mcp-dev/run-typecheck.md
What run_typecheck does on Mcp Dev
AI agents invoke run_typecheck to trigger actions in Mcp Dev. 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.
Why run_typecheck is rated High
This tool triggers execution of TypeScript's type-checker, which is a subprocess/command invocation. Although tsc --noEmit is read-only (no side effects on disk), the Execute category applies because the tool runs external code/tools whose effects depend on context.
From the tool's definition Tool name is 'run_typecheck' and description states 'Run TypeScript type-checking (tsc --noEmit)' — it executes an external command (tsc) whose behavior depends on arguments and codebase state.
Attacks that exploit this kind of access
The rule that runs run_typecheck safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_typecheck, this is the rule to start with:
run_typecheck 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every run_typecheck call is checked against it from then on.
Questions about run_typecheck
Run TypeScript type-checking (tsc --noEmit) for a service. Returns structured errors with file, line, column, and message. Call after writing code to verify correctness before committing. It is categorised as a Execute tool in the Mcp Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for run_typecheck: 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 Mcp Dev. Nothing to install.
run_typecheck 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 run_typecheck 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 run_typecheck. 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.
run_typecheck is provided by the Mcp Dev MCP server (2loch-ness6/mempalace-mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
Across the catalogue