zernio_list_custom_fields

List all custom contact fields defined in your Zernio account.

SERVERZernio SOURCEeyalm321/zernio-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eyalm321-zernio-mcp/zernio-list-custom-fields.md

What zernio_list_custom_fields does on Zernio

AI agents call zernio_list_custom_fields to retrieve information from Zernio without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why zernio_list_custom_fields is rated Low

This tool queries and retrieves metadata about custom contact fields within the Zernio account. It performs a read-only operation that returns information without altering any data, executing external operations, or creating financial obligations. The low severity reflects minimal blast radius if misused by an agent — it only exposes the schema/structure of custom fields, not sensitive contact data itself.

From the tool's definition Tool name contains 'list' and description states 'List all custom contact fields' — a retrieval operation with no modification, deletion, or side effects.

Questions about zernio_list_custom_fields

What does the zernio_list_custom_fields tool do? +

List all custom contact fields defined in your Zernio account. It is categorised as a Read tool in the Zernio MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zernio_list_custom_fields? +

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

What risk level is zernio_list_custom_fields? +

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

Can I rate-limit zernio_list_custom_fields? +

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

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

zernio_list_custom_fields is provided by the Zernio MCP server (eyalm321/zernio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Zernio, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Zernio's. Pull the full record:

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.