testing · Project Graph MCP: Risk & Policy

WHAT IT DOES

What testing does on Project Graph

AI agents use testing to create or update resources in Project Graph — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Graph environment.

WHY IT NEEDS A POLICY

Why testing needs a policy

This tool manages a test checklist with actions to mark tests as pending, pass, or fail, and to reset the checklist. The 'reset' action could clear test state, but overall these are reversible state changes to a checklist (marking statuses). Write is the most appropriate category since it modifies test tracking data.

From the tool's definition Test checklist management. Actions: pending|pass|fail|summary|reset

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

testing Rate-limited

testing stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "testing": {
      "limits": [
        {
          "counter": "testing_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 Graph, so you can run agents against it safely.

FAQ

Questions about testing

What does the testing tool do? +

Test checklist management. Actions: pending|pass|fail|summary|reset. It is categorised as a Write tool in the Project Graph MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on testing? +

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

What risk level is testing? +

testing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit testing? +

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

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

testing is provided by the Project Graph MCP server (rnd-pro/project-graph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.