use-local-project
AI agents invoke use-local-project to trigger actions in Mcp Playwright Test. 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.
Although the description is empty (lowering confidence), the tool's name and server context indicate it operates within an automation framework that executes UI and API tests. 'use-local-project' most likely loads or switches to a local project context, enabling subsequent test execution.
From the tool's definition Tool named 'use-local-project' belongs to a Playwright testing automation server alongside tools like 'execute-ui-tests', 'execute-api-tests', 'launch-browser', and 'clone-repository'.
Attacks that exploit this kind of access
use-local-project. It is categorised as a Execute tool in the Mcp Playwright Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Playwright Test MCP server in PolicyLayer and add a rule for use-local-project: 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 Playwright Test. Nothing to install.
use-local-project 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 use-local-project 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 use-local-project. 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.
use-local-project is provided by the Mcp Playwright Test MCP server (w1561778301/mcp-playwright-test). 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 →