Get plans, pricing, and terms for a specific Texas utility provider — use after search_utility_providers has narrowed the list and the user wants to drill into one option. Use when the user says 'tell me more about Reliant', 'what are Gexa's plans for my Austin apartment', or 'show me the contrac...
Part of the Utilify server.
Free to start. No card required.
AI agents call get_provider_details 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 get_provider_details 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": {
"get_provider_details": {}
}
}See the full Utilify policy for all 8 tools.
These attack patterns abuse exactly the kind of access get_provider_details 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.
Get plans, pricing, and terms for a specific Texas utility provider — use after search_utility_providers has narrowed the list and the user wants to drill into one option. Use when the user says 'tell me more about Reliant', 'what are Gexa's plans for my Austin apartment', or 'show me the contract details before I pick one'. Returns available plans at the given ZIP with rates, contract length, early-termination fees, and signup requirements. Pass zip_code whenever the user has given an address — the plan list is TDU-filtered to that ZIP, so omitting it returns the provider's full statewide catalog rather than what's actually buyable. Don't use this to discover providers (use search_utility_providers) or to compare across REPs (use compare_providers).. 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 get_provider_details: 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.
get_provider_details 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 get_provider_details 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 get_provider_details. 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.
get_provider_details 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.