Low Risk

get_users

Get all users from your Grocy instance.

How to control get_users ↓

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

Low Risk

Even though get_users only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsBulk/mass operation — affects multiple targets

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

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

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

get_users 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 MCP Grocy API — 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_users tool do? +

Get all users from your Grocy instance. It is categorised as a Read tool in the MCP Grocy API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_users? +

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

What risk level is get_users? +

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

Can I rate-limit get_users? +

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

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

get_users is provided by the MCP Grocy API MCP server (saya6k/mcp-grocy-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Grocy API tool call.

Deterministic rules across all 37 MCP Grocy API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

37 MCP Grocy API 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.