Retrieve user locations (seats) with optional campus, host, and activity filters
AI agents call getLocations 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 location/seat information with optional filtering parameters. The verb 'Retrieve' and the absence of any modification, deletion, or execution language clearly place this in the Read category. The data returned (physical locations/seats) is informational and non-sensitive compared to financial or destructive operations.
From the tool's definition Tool name 'getLocations' and description 'Retrieve user locations (seats) with optional campus, host, and activity filters' indicate a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Retrieve user locations (seats) with optional campus, host, and activity filters. 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 getLocations: 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.
getLocations 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 getLocations 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 getLocations. 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.
getLocations 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 →