Runs mypy and returns structured type-check diagnostics (file, line, severity, message, code).
AI agents invoke mypy to trigger actions in Make. 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 tool executes the mypy type checker as an external process. While mypy is a read-only static analysis tool, executing external processes falls under the Execute category. The blast radius is medium since it only runs type analysis and does not modify or delete files, but arbitrary code execution contexts can be unpredictable depending on the environment.
From the tool's definition 'Runs mypy' — explicitly runs an external tool/process to perform type checking
Documented attack patterns abuse exactly the kind of access mypy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for mypy:
{
"version": "1",
"default": "deny",
"tools": {
"mypy": {
"limits": [
{
"counter": "mypy_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}mypy 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.
Runs mypy and returns structured type-check diagnostics (file, line, severity, message, code). It is categorised as a Execute tool in the Make MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Make MCP server in PolicyLayer and add a rule for mypy: 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 Make. Nothing to install.
mypy 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 mypy 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 mypy. 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.
mypy is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, 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.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.