test-progress-method
Tests the this.progress() method for sending progress notifications
This record as markdown: /tools/frontmcp/test-progress-method.md
What test-progress-method does on Frontmcp
AI agents invoke test-progress-method to trigger actions in Frontmcp. 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 test-progress-method is rated High
This tool executes a test of the progress notification method, triggering external operations (sending notifications). It runs code/triggers operations rather than simply reading or writing data. Severity is medium as misuse could spam notifications or reveal system behavior, but blast radius is limited.
From the tool's definition 'Tests the this.progress() method for sending progress notifications'
Attacks that exploit this kind of access
The rule that runs test-progress-method safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test-progress-method, this is the rule to start with:
test-progress-method 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every test-progress-method call is checked against it from then on.
Questions about test-progress-method
Tests the this.progress() method for sending progress notifications. It is categorised as a Execute tool in the Frontmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Front MCP server in PolicyLayer and add a rule for test-progress-method: 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 Frontmcp. Nothing to install.
test-progress-method 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 test-progress-method 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 test-progress-method. 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.
test-progress-method is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
Across the catalogue