Run Lupa tests and return structured JSON results. Use this to identify failing tests.
AI agents invoke lupa_run_tests to trigger actions in Lupa 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 executes test code whose behavior depends entirely on the test files and their contents. While test execution is typically a development activity, an AI agent misusing this tool could trigger tests that modify system state, access sensitive data, make external requests, or cause other unpredictable effects.
From the tool's definition Tool description states 'Run Lupa tests and return structured JSON results' — the verb 'run' indicates code execution.
Attacks that exploit this kind of access
Run Lupa tests and return structured JSON results. Use this to identify failing tests. It is categorised as a Execute tool in the Lupa MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Lupa MCP Server MCP server in PolicyLayer and add a rule for lupa_run_tests: 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 Lupa MCP Server. Nothing to install.
lupa_run_tests 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 lupa_run_tests 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 lupa_run_tests. 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.
lupa_run_tests is provided by the Lupa MCP Server MCP server (pawel-up/lupa-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →