List all custom fields for accounts
AI agents call list_account_custom_fields to retrieve information from Frontapp 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 account custom field metadata. It performs no creation, modification, deletion, or execution of external operations. The 'list' verb and retrieval-only nature clearly place it in the Read category. Severity is low as it exposes schema/configuration information without accessing sensitive customer data or enabling harmful actions.
From the tool's definition Tool name 'list_account_custom_fields' and description 'List all custom fields for accounts' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_account_custom_fields gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Frontapp MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_account_custom_fields:
{
"version": "1",
"default": "deny",
"tools": {
"list_account_custom_fields": {}
}
}list_account_custom_fields is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all custom fields for accounts. It is categorised as a Read tool in the Frontapp MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Frontapp MCP Server MCP server in PolicyLayer and add a rule for list_account_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 Frontapp MCP Server. Nothing to install.
list_account_custom_fields 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 list_account_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.
Set action: deny in the PolicyLayer policy for list_account_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.
list_account_custom_fields is provided by the Frontapp MCP Server MCP server (zqushair/frontapp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Frontapp MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
151 Frontapp MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.