Retrieve campus-user associations by campusId or userId
AI agents call getCampusUsers 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 existing data about campus-user associations without creating, modifying, deleting, or executing operations. While it accesses potentially sensitive user information (which could elevate concern in an information security context), the functional capability itself is read-only with minimal blast radius if misused by an agent—exposure of directory/association data is the primary risk, not…
From the tool's definition Tool name 'getCampusUsers' and description 'Retrieve campus-user associations' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Retrieve campus-user associations by campusId or userId. 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 getCampusUsers: 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.
getCampusUsers 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 getCampusUsers 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 getCampusUsers. 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.
getCampusUsers 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 →