Batch-parse messy international phone numbers and addresses into structured E.164 phones, split address fields, and confidence flags.
Part of the Useful AI server.
Free to start. No card required.
AI agents call useful_contact_entry_parser to retrieve information from Useful AI 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 useful_contact_entry_parser 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": {
"useful_contact_entry_parser": {}
}
}See the full Useful AI policy for all 27 tools.
These attack patterns abuse exactly the kind of access useful_contact_entry_parser 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.
Batch-parse messy international phone numbers and addresses into structured E.164 phones, split address fields, and confidence flags.. It is categorised as a Read tool in the Useful AI MCP Server, which means it retrieves data without modifying state.
Register the Useful AI MCP server in PolicyLayer and add a rule for useful_contact_entry_parser: 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 Useful AI. Nothing to install.
useful_contact_entry_parser 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 useful_contact_entry_parser 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 useful_contact_entry_parser. 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.
useful_contact_entry_parser is provided by the Useful AI MCP server (useful-ai/useful-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 27 Useful AI 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.