amocrm_list_event_types
List the catalog of ~50 event types (read-only meta).
This record as markdown: /tools/allmcp/amocrm-list-event-types.md
What amocrm_list_event_types does on Allmcp
AI agents call amocrm_list_event_types 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.
Why amocrm_list_event_types is rated Low
This tool retrieves a static catalog of event types from AmoCRM without modifying, deleting, or executing any operations. It is purely informational metadata retrieval, fitting the Read category. Severity is low because exposing event type metadata poses minimal security risk.
From the tool's definition Tool name includes 'list' and description explicitly states 'read-only meta' with no side effects.
Attacks that exploit this kind of access
The rule that runs amocrm_list_event_types 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_list_event_types, this is the rule to start with:
amocrm_list_event_types 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 Allmcp, apply this rule, and every amocrm_list_event_types call is checked against it from then on.
Questions about amocrm_list_event_types
List the catalog of ~50 event types (read-only meta). It is categorised as a Read tool in the Allmcp MCP Server, which means it retrieves data without modifying state.
Register the All MCP server in PolicyLayer and add a rule for amocrm_list_event_types: 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.
amocrm_list_event_types 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 amocrm_list_event_types 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 amocrm_list_event_types. 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.
amocrm_list_event_types 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.
More on All, and thousands of servers like it.
This server
Across the catalogue