Get candidate details with enriched filtering data including subscription status, activity status, and location info. Useful for subscriber reports and filtering.
AI agents call get_candidate_with_filters 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.
This tool retrieves candidate information with various filters applied. It performs a query operation that returns data without any side effects—no creation, modification, deletion, or execution of code/commands. The enriched filtering includes subscription and activity status, but these are read parameters, not modifications. This is a straightforward Read category operation used for reporting and analysis.
From the tool's definition Tool name 'get_candidate_with_filters' and description states 'Get candidate details with enriched filtering data including subscription status, activity status, and location info.' The verb 'Get' and phrase 'candidate details' indicate pure data retrieval…
Attacks that exploit this kind of access
Get candidate details with enriched filtering data including subscription status, activity status, and location info. Useful for subscriber reports and filtering. It is categorised as a Read tool in the Viterbit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Viterbit MCP Server MCP server in PolicyLayer and add a rule for get_candidate_with_filters: 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.
get_candidate_with_filters 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 get_candidate_with_filters 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 get_candidate_with_filters. 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.
get_candidate_with_filters 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.
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 →