mautic_check_user_permissions

Check specific permissions for a user. Useful for diagnosing 403 errors.

SERVERMcp Mautic SOURCEesanum/mcp-mautic

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/esanum-mcp-mautic/mautic-check-user-permissions.md

WHAT IT DOES

What mautic_check_user_permissions does on Mcp Mautic

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

RISK

Why mautic_check_user_permissions is rated Low

This tool retrieves permission information about a user without modifying any data or triggering side effects. It is a read-only diagnostic utility that queries the state of user permissions in the Mautic system.

From the tool's definition Tool name contains 'check' and description states it checks/queries 'specific permissions for a user' with no mention of modification, deletion, or execution of actions. It is explicitly diagnostic in nature ('Useful for diagnosing 403 errors').

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mautic_check_user_permissions safely

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

mautic_check_user_permissions Allowed

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

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

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

FAQ

Questions about mautic_check_user_permissions

What does the mautic_check_user_permissions tool do? +

Check specific permissions for a user. Useful for diagnosing 403 errors. It is categorised as a Read tool in the Mcp Mautic MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mautic_check_user_permissions? +

Register the Mcp Mautic MCP server in PolicyLayer and add a rule for mautic_check_user_permissions: 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 Mcp Mautic. Nothing to install.

What risk level is mautic_check_user_permissions? +

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

Can I rate-limit mautic_check_user_permissions? +

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

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

mautic_check_user_permissions is provided by the Mcp Mautic MCP server (esanum/mcp-mautic). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Mautic, and thousands of servers like it.

This server

All 229 Mcp Mautic tools →

Across the catalogue

The MCP Attack Database →

Guides

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