get_custom_field
Get a specific custom field definition by ID
This record as markdown: /tools/instantkom-mcp-server/get-custom-field.md
What get_custom_field does on instantKOM MCP Server
AI agents call get_custom_field to retrieve information from instantKOM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_custom_field is rated Low
The tool performs a data retrieval operation (get/fetch) returning a custom field definition. There is no data modification, deletion, code execution, or financial implication. This is a classic Read category tool with minimal blast radius if misused—an AI agent could only retrieve field metadata that may already be accessible.
From the tool's definition Tool name and description indicate retrieval of a custom field definition: 'Get a specific custom field definition by ID'. This is a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_custom_field safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_custom_field, this is the rule to start with:
get_custom_field is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every get_custom_field call is checked against it from then on.
Questions about get_custom_field
Get a specific custom field definition by ID. It is categorised as a Read tool in the instantKOM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for get_custom_field: 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 instantKOM MCP Server. Nothing to install.
get_custom_field 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_field 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_field. 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_field is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
This server
Across the catalogue