List test files resolved by Lupa config without running tests or starting Vite/Playwright.
AI agents call lupa_list_test_files to retrieve information from Lupa MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns metadata about test files that match the Lupa configuration. It does not execute code, modify data, delete anything, or trigger external operations beyond resolving a configuration. The absence of side effects and the explicit mention of not running tests or starting services confirms it is a safe read operation with low blast radius if misused.
From the tool's definition Tool description explicitly states 'List test files' without running tests or modifying state. The verb 'list' is a read-only operation that retrieves and returns information about test files.
Attacks that exploit this kind of access
List test files resolved by Lupa config without running tests or starting Vite/Playwright. It is categorised as a Read tool in the Lupa MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lupa MCP Server MCP server in PolicyLayer and add a rule for lupa_list_test_files: 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_list_test_files is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lupa_list_test_files 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_list_test_files. 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_list_test_files 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 →