util_return_pct
Compute percent return between start and end values.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/util-return-pct.md
What util_return_pct does on Delx MCP Server
AI agents invoke util_return_pct to trigger actions in Delx 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | number | Yes | Ending value for percent return. |
start | number | Yes | Starting value for percent return. |
Parameters from the server's own tool schema.
Why util_return_pct is rated High
util_return_pct triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs util_return_pct safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_return_pct, this is the rule to start with:
util_return_pct 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 Delx MCP Server, apply this rule, and every util_return_pct call is checked against it from then on.
Questions about util_return_pct
Compute percent return between start and end values. It is categorised as a Execute tool in the Delx MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
util_return_pct accepts 2 parameters: end, start. Required: end, start. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for util_return_pct: 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 Delx MCP Server. Nothing to install.
util_return_pct 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 util_return_pct 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 util_return_pct. 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.
util_return_pct is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
Across the catalogue