Low Risk

list_grants

List grants for a restricted user

How to control list_grants ↓

What list_grants does on Linode MCP Server

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

Low Risk

Why list_grants needs a policy

This tool retrieves and displays existing grant information for a user account. It is a read-only operation with no side effects, no code execution, and no data modification. The blast radius is minimal since it only exposes existing permission metadata that an authorized user would typically be able to query anyway.

From the tool's definition Tool name 'list_grants' and description 'List grants for a restricted user' indicate a query operation that retrieves authorization/permission data without modifying or executing any actions.

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

How to control list_grants

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

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

list_grants 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 Linode MCP Server — 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.

Related tools and policies

Go deeper

Questions about list_grants

What does the list_grants tool do? +

List grants for a restricted user. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_grants? +

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

What risk level is list_grants? +

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

Can I rate-limit list_grants? +

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

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

list_grants is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linode MCP Server tool call.

Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ 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.