Load permission dictionary, object labels, system settings, and existing permission sets for governance design.
AI agents call get_permission_set_editor to retrieve information from Sanka 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 and queries existing permission configurations and metadata without modifying, executing code, deleting, or committing financial transactions. It's a pure data retrieval operation that an editor UI would use to display current permission states.
From the tool's definition The tool description explicitly states it 'Load[s] permission dictionary, object labels, system settings, and existing permission sets' — all read operations that retrieve configuration data for governance design purposes.
Attacks that exploit this kind of access
Load permission dictionary, object labels, system settings, and existing permission sets for governance design. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for get_permission_set_editor: 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 Sanka MCP Server. Nothing to install.
get_permission_set_editor 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_permission_set_editor 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_permission_set_editor. 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_permission_set_editor is provided by the Sanka MCP Server MCP server (sankahq/sanka-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 →