search_candidates_by_location

Search candidates by geographic location using zones, provinces, cities, or address information.

Server Viterbit MCP Server techkampe/mcp_viterbit
Category Read
Risk class Low
Parameters 00 required

What search_candidates_by_location does on Viterbit MCP Server

AI agents call search_candidates_by_location to retrieve information from Viterbit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_candidates_by_location needs a policy

This tool queries candidate data filtered by geographic parameters (zones, provinces, cities, addresses). It is a read-only search operation that retrieves existing information without creating, modifying, deleting, or executing operations. The low severity reflects minimal risk if misused — exposure of candidate location data is a privacy concern but not immediately destructive or financial in nature.

From the tool's definition Tool name contains 'search' and description states it 'Search candidates by geographic location' — a retrieval operation with no modification or side effects.

Questions about search_candidates_by_location

What does the search_candidates_by_location tool do? +

Search candidates by geographic location using zones, provinces, cities, or address information. It is categorised as a Read tool in the Viterbit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_candidates_by_location? +

Register the Viterbit MCP Server MCP server in PolicyLayer and add a rule for search_candidates_by_location: 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 Viterbit MCP Server. Nothing to install.

What risk level is search_candidates_by_location? +

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

Can I rate-limit search_candidates_by_location? +

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

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

search_candidates_by_location is provided by the Viterbit MCP Server MCP server (techkampe/mcp_viterbit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.