amocrm_get_custom_field

A read tool on the All MCP server.

SERVERAllmcp SOURCEPerception-Dynamics-Inc/allmcp

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/allmcp/amocrm-get-custom-field.md

WHAT IT DOES

What amocrm_get_custom_field does on Allmcp

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

RISK

Why amocrm_get_custom_field is rated Low

The 'get' prefix and sibling tools showing clear patterns (create/delete/get operations) suggest this retrieves custom field data from AmoCRM. Read operations have low severity as they do not modify state or cause irreversible changes. Confidence reduced to 0.8 due to empty description, but naming convention strongly indicates a retrieval operation.

From the tool's definition Tool name 'amocrm_get_custom_field' contains 'get', indicating data retrieval without modification. Description is empty, limiting full certainty of intent.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs amocrm_get_custom_field safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For amocrm_get_custom_field, this is the rule to start with:

amocrm_get_custom_field Allowed

amocrm_get_custom_field is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "amocrm_get_custom_field": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every amocrm_get_custom_field call is checked against it from then on.

FAQ

Questions about amocrm_get_custom_field

What does the amocrm_get_custom_field tool do? +

amocrm_get_custom_field is a read tool on the All MCP server. It is categorised as a Read tool in the Allmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on amocrm_get_custom_field? +

Register the All MCP server in PolicyLayer and add a rule for amocrm_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 Allmcp. Nothing to install.

What risk level is amocrm_get_custom_field? +

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

Can I rate-limit amocrm_get_custom_field? +

Yes. Add a rate_limit block to the amocrm_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.

How do I block amocrm_get_custom_field completely? +

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

What MCP server provides amocrm_get_custom_field? +

amocrm_get_custom_field is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on All, and thousands of servers like it.

This server

All 501 All tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →