Low Risk

test_progress

Test tool to verify progress reporting works in DynamicFastMCP.

How to control test_progress ↓

AI agents call test_progress to retrieve information from Preloop without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Even though test_progress only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Documented attack patterns abuse exactly the kind of access test_progress gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Preloop, and nothing reaches the server without passing your rules. This is the rule we recommend for test_progress:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_progress": {}
  }
}

test_progress is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Preloop — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the test_progress tool do? +

Test tool to verify progress reporting works in DynamicFastMCP. It is categorised as a Read tool in the Preloop MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on test_progress? +

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

What risk level is test_progress? +

test_progress is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit test_progress? +

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

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

test_progress is provided by the Preloop MCP server (preloop/preloop). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Preloop tool call.

Deterministic rules across all 15 Preloop tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

15 Preloop tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.