amocrm_get_user

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-user.md

WHAT IT DOES

What amocrm_get_user does on Allmcp

AI agents call amocrm_get_user 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_user is rated Low

The 'get' prefix in the tool name indicates this is a retrieval operation that queries user information without modifying, deleting, or executing external operations. Even without a description, this follows standard API naming conventions for read operations. Confidence is slightly reduced due to missing description, but the naming pattern is clear.

From the tool's definition Tool name 'amocrm_get_user' indicates a retrieval operation ('get') on user data. No description provided, but 'get' convention strongly suggests read-only data access.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs amocrm_get_user 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_user, this is the rule to start with:

amocrm_get_user Allowed

amocrm_get_user 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_user": {}
  }
}

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_user call is checked against it from then on.

FAQ

Questions about amocrm_get_user

What does the amocrm_get_user tool do? +

amocrm_get_user 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_user? +

Register the All MCP server in PolicyLayer and add a rule for amocrm_get_user: 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_user? +

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

Can I rate-limit amocrm_get_user? +

Yes. Add a rate_limit block to the amocrm_get_user 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_user completely? +

Set action: deny in the PolicyLayer policy for amocrm_get_user. 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_user? +

amocrm_get_user 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 →