list_permission_sets
Review permission sets for Sanka workspace governance and access-control planning.
This record as markdown: /tools/sankahq-sanka-mcp/list-permission-sets.md
What list_permission_sets does on Sanka MCP Server
AI agents call list_permission_sets to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_permission_sets is rated Low
This tool retrieves and displays permission sets for governance and access-control planning purposes. It queries existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an AI agent could at most view access-control metadata, which is informational only. No permissions would be altered, no code executed, and no data destroyed or modified.
From the tool's definition Tool name 'list_permission_sets' and description 'Review permission sets' indicates a query/retrieval operation with no modification or side effects. The verb 'Review' and 'list' are characteristic of read-only data retrieval.
Attacks that exploit this kind of access
The rule that runs list_permission_sets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_permission_sets, this is the rule to start with:
list_permission_sets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every list_permission_sets call is checked against it from then on.
Questions about list_permission_sets
Review permission sets for Sanka workspace governance and access-control planning. 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 list_permission_sets: 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.
list_permission_sets 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 list_permission_sets 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 list_permission_sets. 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.
list_permission_sets 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.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue