Execute all custom rules against code or a file.
AI agents invoke execute_custom_rules to trigger actions in Tech Debt 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.
This tool runs custom rules against code, which qualifies as Execute rather than Read because it actively triggers rule evaluation logic that can have side effects depending on what those rules do. While the immediate output is analysis, 'execute' indicates active computation/triggering of external logic.
From the tool's definition Tool name 'execute_custom_rules' and description 'Execute all custom rules against code or a file' explicitly indicates code execution.
Documented attack patterns abuse exactly the kind of access execute_custom_rules gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tech Debt MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_custom_rules:
{
"version": "1",
"default": "deny",
"tools": {
"execute_custom_rules": {
"limits": [
{
"counter": "execute_custom_rules_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_custom_rules 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.
Execute all custom rules against code or a file. It is categorised as a Execute tool in the Tech Debt MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tech Debt MCP Server MCP server in PolicyLayer and add a rule for execute_custom_rules: 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 Tech Debt MCP Server. Nothing to install.
execute_custom_rules 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 execute_custom_rules 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 execute_custom_rules. 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.
execute_custom_rules is provided by the Tech Debt MCP Server MCP server (pierrejanineh/techdebtmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tech Debt 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.
16 Tech Debt MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.