Get the configuration of a custom field by UID.
AI agents call get_custom_field_config to retrieve information from InvGate Service Desk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data about a custom field. It performs a read-only query operation with no capability to modify, delete, or execute actions. The blast radius of misuse is minimal — an agent could only learn about field configurations, which is informational data. No destructive, financial, or operational impact is possible.
From the tool's definition Tool name is 'get_custom_field_config' and description states 'Get the configuration of a custom field by UID' — uses the verb 'Get' indicating data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get the configuration of a custom field by UID. It is categorised as a Read tool in the InvGate Service Desk MCP Server, which means it retrieves data without modifying state.
Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for get_custom_field_config: 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 InvGate Service Desk. Nothing to install.
get_custom_field_config 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_config 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_config. 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_config is provided by the InvGate Service Desk MCP server (oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0). 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 →