leie_search_exclusions
Search the self-hosted HHS OIG LEIE by individual or business name, with optional two-letter state and a bounded result limit. Returns evidence IDs for follow-up. Name similarity alone does not establish identity.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/leie-search-exclusions.md
What leie_search_exclusions does on Livedatalink
AI agents call leie_search_exclusions to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Individual or business name, at least 2 characters. |
limit | integer | — | Maximum rows, default 10 and maximum 50. |
state | string | — | Optional two-letter US state code. |
Parameters from the server's own tool schema.
Why leie_search_exclusions is rated Low
Even though leie_search_exclusions 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.
Attacks that exploit this kind of access
The rule that runs leie_search_exclusions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For leie_search_exclusions, this is the rule to start with:
leie_search_exclusions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every leie_search_exclusions call is checked against it from then on.
Questions about leie_search_exclusions
Search the self-hosted HHS OIG LEIE by individual or business name, with optional two-letter state and a bounded result limit. Returns evidence IDs for follow-up. Name similarity alone does not establish identity. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
leie_search_exclusions accepts 3 parameters: name, limit, state. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for leie_search_exclusions: 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 Livedatalink. Nothing to install.
leie_search_exclusions 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 leie_search_exclusions 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 leie_search_exclusions. 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.
leie_search_exclusions is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue