Low Risk

getRoles

Get roles from Directus

Accepts URL/endpoint input (url); Accepts freeform code/query input (query); Handles credentials or secrets (token)

Part of the Directus MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

pixelsock/directus-mcp Read Risk 3/5

AI agents call getRoles to retrieve information from Directus MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though getRoles only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

pixelsock-directus-mcp.yaml
tools:
  getRoles:
    rules:
      - action: allow

See the full Directus MCP Server policy for all 18 tools.

Tool Name getRoles
Category Read
Risk Level Low

View all 18 tools →

Agents calling read-class tools like getRoles have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the getRoles tool do? +

Get roles from Directus. It is categorised as a Read tool in the Directus MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getRoles? +

Add a rule in your Intercept YAML policy under the tools section for getRoles. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Directus MCP Server MCP server.

What risk level is getRoles? +

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

Can I rate-limit getRoles? +

Yes. Add a rate_limit block to the getRoles rule in your Intercept 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 getRoles completely? +

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

getRoles is provided by the Directus MCP Server MCP server (pixelsock/directus-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Directus MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.