Low Risk

get_access_rights

get_access_rights

How to control get_access_rights ↓

AI agents call get_access_rights to retrieve information from 1C MCP Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The tool retrieves access control information from a 1C:Enterprise database, which is fundamentally a Read operation (no data modification). However, confidence is moderate (0.72) due to missing description. Severity is medium because exposed access rights metadata could inform privilege escalation attacks, though the tool itself only retrieves rather than modifies permissions.

From the tool's definition Tool name 'get_access_rights' indicates retrieval of permission/security metadata. No description provided, but the read-like verb 'get' and absence of destructive/modifying keywords suggest query-only behavior.

Documented attack patterns abuse exactly the kind of access get_access_rights gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and 1C MCP Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for get_access_rights:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_access_rights": {}
  }
}

get_access_rights is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register 1C MCP Toolkit — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_access_rights tool do? +

get_access_rights. It is categorised as a Read tool in the 1C MCP Toolkit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_access_rights? +

Register the 1C MCP Toolkit MCP server in PolicyLayer and add a rule for get_access_rights: 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 1C MCP Toolkit. Nothing to install.

What risk level is get_access_rights? +

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

Can I rate-limit get_access_rights? +

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

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

get_access_rights is provided by the 1C MCP Toolkit MCP server (roctup/1c-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 1C MCP Toolkit tool call.

Deterministic rules across all 13 1C MCP Toolkit tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

13 1C MCP Toolkit tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.