test_endpoint · GASSAPI MCP Server MCP: Risk & Policy

WHAT IT DOES

What test_endpoint does on GASSAPI MCP Server

AI agents invoke test_endpoint to trigger actions in GASSAPI 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.

WHY IT NEEDS A POLICY

Why test_endpoint needs a policy

Testing an endpoint executes an actual HTTP request to an external system, which constitutes an external operation. While it is read-like in intent, it triggers real side effects on external services depending on the endpoint being tested (e.g., POST, PUT, DELETE endpoints). This makes it Execute rather than Read. Severity is medium because misuse could trigger unintended operations on external APIs.

From the tool's definition 'Test a single endpoint with optional environment variables' — triggers an external HTTP request/operation against an API endpoint

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_endpoint Rate-limited

test_endpoint 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_endpoint": {
      "limits": [
        {
          "counter": "test_endpoint_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 GASSAPI MCP Server, so you can run agents against it safely.

FAQ

Questions about test_endpoint

What does the test_endpoint tool do? +

Test a single endpoint with optional environment variables. It is categorised as a Execute tool in the GASSAPI MCP Server 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_endpoint? +

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

What risk level is test_endpoint? +

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

Can I rate-limit test_endpoint? +

Yes. Add a rate_limit block to the test_endpoint 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_endpoint completely? +

Set action: deny in the PolicyLayer policy for test_endpoint. 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_endpoint? +

test_endpoint is provided by the GASSAPI MCP Server MCP server (martin-1103/mcp2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.