swiftsign_list_templates

List your saved templates. Scoped to your key's mode — sandbox (sk_test_) keys see test templates, live keys see live.

SERVERMcp SOURCEhttps://swiftsign.ca/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ca-swiftsign-mcp/swiftsign-list-templates.md

WHAT IT DOES

What swiftsign_list_templates does on Mcp

AI agents call swiftsign_list_templates to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why swiftsign_list_templates is rated Low

This tool retrieves and lists template data that already exists in the system. It is a read-only query operation with no capacity to create, modify, delete, or execute external actions. The low severity reflects minimal blast radius — even if an agent lists all templates, no data is altered or financial operations occur.

From the tool's definition Tool name 'list_templates' and description 'List your saved templates' indicate a retrieval operation with no side effects. The description explicitly states it queries templates scoped to the API key's mode without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs swiftsign_list_templates safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For swiftsign_list_templates, this is the rule to start with:

swiftsign_list_templates Allowed

swiftsign_list_templates is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "swiftsign_list_templates": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every swiftsign_list_templates call is checked against it from then on.

FAQ

Questions about swiftsign_list_templates

What does the swiftsign_list_templates tool do? +

List your saved templates. Scoped to your key's mode — sandbox (sk_test_) keys see test templates, live keys see live. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on swiftsign_list_templates? +

Register the MCP server in PolicyLayer and add a rule for swiftsign_list_templates: 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 Mcp. Nothing to install.

What risk level is swiftsign_list_templates? +

swiftsign_list_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit swiftsign_list_templates? +

Yes. Add a rate_limit block to the swiftsign_list_templates 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.

How do I block swiftsign_list_templates completely? +

Set action: deny in the PolicyLayer policy for swiftsign_list_templates. 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.

What MCP server provides swiftsign_list_templates? +

swiftsign_list_templates is provided by the MCP server (https://swiftsign.ca/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 10 tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →