Get all available custom field definitions and their schemas from Viterbit. Useful for understanding field structure and IDs.
AI agents call get_custom_fields_definitions 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 queries and returns metadata about custom field definitions and their schemas from the Viterbit recruitment system. It performs a read-only operation that retrieves structural information without creating, modifying, deleting, or executing any operations. The low severity reflects minimal risk if misused—an AI agent obtaining field definitions cannot directly harm candidate data or recruitment processes.
From the tool's definition Tool name 'get_custom_fields_definitions' and description 'Get all available custom field definitions and their schemas' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all available custom field definitions and their schemas from Viterbit. Useful for understanding field structure and IDs. 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_custom_fields_definitions: 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_custom_fields_definitions 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_custom_fields_definitions 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_custom_fields_definitions. 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_custom_fields_definitions 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 →