Retrieve clusters with optional campusId and/or name filter (requires Basic staff role)
AI agents call getClusters to retrieve information from 42 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves cluster information from the 42 intranet API with optional filtering. It performs no data modification, deletion, or external execution. The access is restricted to staff roles, limiting blast radius. Classification as Read with low severity is appropriate for querying campus infrastructure data without side effects.
From the tool's definition Tool description states 'Retrieve clusters' with optional filters (campusId, name). The verb 'Retrieve' and lack of any modification or deletion language indicate a read-only operation. Requires 'Basic staff role' showing access control is enforced.
Attacks that exploit this kind of access
Retrieve clusters with optional campusId and/or name filter (requires Basic staff role). It is categorised as a Read tool in the 42 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 42 MCP Server MCP server in PolicyLayer and add a rule for getClusters: 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 42 MCP Server. Nothing to install.
getClusters is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getClusters 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.
Set action: deny in the PolicyLayer policy for getClusters. 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.
getClusters is provided by the 42 MCP Server MCP server (smizuoch/42-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →