Get the spaces (rooms/areas) associated with a scheduled maintenance item.
AI agents call get-maintenance-spaces to retrieve information from Cpp Espace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about spaces linked to a maintenance schedule. It performs a query operation that returns data without creating, modifying, deleting, or executing external actions. The 'Get' prefix and absence of any mutation language confirm this is a safe read operation with minimal blast radius.
From the tool's definition Tool name 'get-maintenance-spaces' and description 'Get the spaces (rooms/areas) associated with a scheduled maintenance item' indicate a read-only retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Get the spaces (rooms/areas) associated with a scheduled maintenance item. It is categorised as a Read tool in the Cpp Espace MCP Server, which means it retrieves data without modifying state.
Register the Cpp Espace MCP server in PolicyLayer and add a rule for get-maintenance-spaces: 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 Cpp Espace. Nothing to install.
get-maintenance-spaces 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 get-maintenance-spaces 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 get-maintenance-spaces. 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.
get-maintenance-spaces is provided by the Cpp Espace MCP server (norm613/cpp-espace-mcp). 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 →