New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

util_url_query_param_diff

URL Query Param Diff finds added, removed, and changed query parameters between URLs from bounded caller-supplied values without an external provider. Call URL Query Param Diff before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evidence, the...

SERVERDelx Mcp A2a SOURCEhttps://api.delx.ai/v1/mcp
Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-url-query-param-diff.md

What util_url_query_param_diff does on Delx Mcp A2a

AI agents call util_url_query_param_diff to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
after_url string Yes After URL supplied to URL Query Param Diff; used only for this bounded calculation and processed in memory without retention.
before_url string Yes Before URL supplied to URL Query Param Diff; used only for this bounded calculation and processed in memory without retention.

Parameters from the server's own tool schema.

Why util_url_query_param_diff is rated Low

Even though util_url_query_param_diff 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.

Questions about util_url_query_param_diff

What does the util_url_query_param_diff tool do? +

URL Query Param Diff finds added, removed, and changed query parameters between URLs from bounded caller-supplied values without an external provider. Call URL Query Param Diff before accepting, caching, redirecting, or retrying a caller-supplied web response. Returns normalized web evidence, the computed finding, and an explicit pass or advisory status for URL Query Param Diff as versioned deterministic JSON. Limitation: Evaluates only caller-supplied metadata; it performs no DNS lookup, HTTP request, web search, credential use, or persistent storage. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.

What parameters does util_url_query_param_diff accept? +

util_url_query_param_diff accepts 2 parameters: after_url, before_url. Required: after_url, before_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_url_query_param_diff? +

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

What risk level is util_url_query_param_diff? +

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

Can I rate-limit util_url_query_param_diff? +

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

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

util_url_query_param_diff is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Delx Mcp A2a, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Delx Mcp A2a's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.