Find VA (Department of Veterans Affairs) facilities by location. Search for VA medical centers, clinics, benefits offices, cemeteries, and vet centers. At least one location parameter should be provided. Args: state: Two-letter state abbreviation (e.g., "CA", "TX"). city: City name to search in. ...
Part of the VA Healthcare Facilities server.
Free to start. No card required.
AI agents call find_va_facilities to retrieve information from VA Healthcare Facilities 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 find_va_facilities 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": {
"find_va_facilities": {}
}
}See the full VA Healthcare Facilities policy for all 3 tools.
These attack patterns abuse exactly the kind of access find_va_facilities 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.
Find VA (Department of Veterans Affairs) facilities by location. Search for VA medical centers, clinics, benefits offices, cemeteries, and vet centers. At least one location parameter should be provided. Args: state: Two-letter state abbreviation (e.g., "CA", "TX"). city: City name to search in. zip_code: 5-digit ZIP code to search near. facility_type: Type of facility — "health" (medical centers/clinics), "benefits" (regional benefits offices), "cemetery" (national cemeteries), or "vet_center" (readjustment counseling). Default "health". limit: Maximum number of results (default 25, max 200).. It is categorised as a Read tool in the VA Healthcare Facilities MCP Server, which means it retrieves data without modifying state.
Register the VA Healthcare Facilities MCP server in PolicyLayer and add a rule for find_va_facilities: 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 VA Healthcare Facilities. Nothing to install.
find_va_facilities 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 find_va_facilities 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 find_va_facilities. 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.
find_va_facilities is provided by the VA Healthcare Facilities MCP server (https://mcp.olyport.com/va-healthcare/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 VA Healthcare Facilities 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.