New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

SERVERMcp Dev SOURCE2loch-ness6/mempalace-mcp-dev
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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.

Questions about run_typecheck

What does the run_typecheck tool do? +

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.

How do I enforce a policy on run_typecheck? +

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.

What risk level is run_typecheck? +

run_typecheck is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_typecheck? +

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.

How do I block run_typecheck completely? +

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.

What MCP server provides run_typecheck? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mcp Dev's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.