Get all event editors for the ministry/organization.
AI agents call get-editors 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 a list of event editors associated with a ministry/organization. The verb 'get' and the read-only nature of listing users (no creation, modification, or deletion) clearly indicate a Read category. The severity is low because access to a list of editors poses minimal risk—it is informational data without destructive or financial implications.
From the tool's definition Tool name 'get-editors' combined with description 'Get all event editors for the ministry/organization' indicates a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get all event editors for the ministry/organization. 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-editors: 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-editors 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-editors 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-editors. 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-editors 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 →