Low Risk

get_provider_detail

Get the full profile of one healthcare service provider identified by slug: company_name, category (plus super_category grouping), description, services_tags (comma-delimited list of services offered), website, phone, city/state, quality_score (0-100), verified status, listing tier (free/paid), p...

Part of the GPH Intelligence — Healthcare Service Provider Finder (API key required) server.

get_provider_detail is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE GPH INTELLIGENCE — HEALTHCARE SERVICE PROVIDER FINDER (API KEY REQUIRED) →

Free to start. No card required.

AI agents call get_provider_detail to retrieve information from GPH Intelligence — Healthcare Service Provider Finder (API key required) 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_detail 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_provider_detail": {}
  }
}

See the full GPH Intelligence — Healthcare Service Provider Finder (API key required) policy for all 3 tools.

Get this rule live on your own GPH Intelligence — Healthcare Service Provider Finder (API key required) server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GPH INTELLIGENCE — HEALTHCARE SERVICE PROVIDER FINDER (API KEY REQUIRED) →

These attack patterns abuse exactly the kind of access get_provider_detail gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_provider_detail only ever does what you allow.

SECURE GPH INTELLIGENCE — HEALTHCARE SERVICE PROVIDER FINDER (API KEY REQUIRED) →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_provider_detail tool do? +

Get the full profile of one healthcare service provider identified by slug: company_name, category (plus super_category grouping), description, services_tags (comma-delimited list of services offered), website, phone, city/state, quality_score (0-100), verified status, listing tier (free/paid), practice_size_fit, and reviews with review_count and average_rating. Slug comes from match_practice or search_providers results. Returns an error if the slug is unknown.. It is categorised as a Read tool in the GPH Intelligence — Healthcare Service Provider Finder (API key required) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_provider_detail? +

Register the GPH Intelligence — Healthcare Service Provider Finder (API key required) MCP server in PolicyLayer and add a rule for get_provider_detail: 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 GPH Intelligence — Healthcare Service Provider Finder (API key required). Nothing to install.

What risk level is get_provider_detail? +

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

Can I rate-limit get_provider_detail? +

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

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

get_provider_detail is provided by the GPH Intelligence — Healthcare Service Provider Finder (API key required) MCP server (https://gph-mcp-server.pages.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GPH Intelligence — Healthcare Service Provider Finder (API key required) tool call.

Deterministic rules across all 3 GPH Intelligence — Healthcare Service Provider Finder (API key required) 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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.