get_presentation_catalog
Read what a Sanka Doc presentation can contain: page sizes (16:9 for screens, A4 landscape for print), layouts, slide blocks with their JSON Schemas and recommended lengths, accents, themes, icons, limits, authoring guidance, the deck JSON Schema and an example deck. Call it once per session befo...
This record as markdown: /tools/sankahq-sanka-mcp/get-presentation-catalog.md
What get_presentation_catalog does on Sanka MCP Server
AI agents call get_presentation_catalog 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 get_presentation_catalog is rated Low
Even though get_presentation_catalog only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_presentation_catalog 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 get_presentation_catalog, this is the rule to start with:
get_presentation_catalog 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 get_presentation_catalog call is checked against it from then on.
Questions about get_presentation_catalog
Read what a Sanka Doc presentation can contain: page sizes (16:9 for screens, A4 landscape for print), layouts, slide blocks with their JSON Schemas and recommended lengths, accents, themes, icons, limits, authoring guidance, the deck JSON Schema and an example deck. Call it once per session before creating or editing presentations, and use only what it lists. 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_presentation_catalog: 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_presentation_catalog 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_presentation_catalog 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_presentation_catalog. 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_presentation_catalog 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