test_web_application · Project Creator MCP: Risk & Policy

WHAT IT DOES

What test_web_application does on Project Creator MCP

AI agents invoke test_web_application to trigger actions in Project Creator MCP. 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.

WHY IT NEEDS A POLICY

Why test_web_application needs a policy

The name suggests running tests against a web application, which falls under Execute (running code/triggering external operations). The server description explicitly mentions 'command execution capabilities', reinforcing this. However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'test_web_application' on a server with 'command execution capabilities'; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_web_application Rate-limited

test_web_application 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_web_application": {
      "limits": [
        {
          "counter": "test_web_application_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Project Creator MCP, so you can run agents against it safely.

FAQ

Questions about test_web_application

What does the test_web_application tool do? +

test_web_application. It is categorised as a Execute tool in the Project Creator MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_web_application? +

Register the Project Creator MCP server in PolicyLayer and add a rule for test_web_application: 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 Project Creator MCP. Nothing to install.

What risk level is test_web_application? +

test_web_application is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_web_application? +

Yes. Add a rate_limit block to the test_web_application 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.

How do I block test_web_application completely? +

Set action: deny in the PolicyLayer policy for test_web_application. 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.

What MCP server provides test_web_application? +

test_web_application is provided by the Project Creator MCP server (jackalterman/project-creator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.