Compare 2–5 Texas utility providers side by side when the user is deciding between specific named options at a new address. Use when the user says 'help me pick between these two', 'which is cheaper for my Dallas home — TXU or Reliant', or 'compare these internet plans before I move in'. Returns ...
Part of the Utilify server.
Free to start. No card required.
AI agents call compare_providers to retrieve information from Utilify without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though compare_providers only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"compare_providers": {}
}
}See the full Utilify policy for all 8 tools.
These attack patterns abuse exactly the kind of access compare_providers gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Compare 2–5 Texas utility providers side by side when the user is deciding between specific named options at a new address. Use when the user says 'help me pick between these two', 'which is cheaper for my Dallas home — TXU or Reliant', or 'compare these internet plans before I move in'. Returns a structured comparison across price, contract terms, features, and ratings so the user can confidently choose one to enroll with. Sequencing: best after search_utility_providers has surfaced the candidate REPs at the address — providers passed here that don't serve the address's TDU will return no plans (electricity is TDU-filtered upstream). Don't use this to compare across utility types (e.g. electricity vs solar) — call search_utility_providers per type instead.. It is categorised as a Read tool in the Utilify MCP Server, which means it retrieves data without modifying state.
Register the Utilify MCP server in PolicyLayer and add a rule for compare_providers: 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 Utilify. Nothing to install.
compare_providers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the compare_providers 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 compare_providers. 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.
compare_providers is provided by the Utilify MCP server (https://utilify.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Utilify tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.