list_provider_keys

List registered BYOK providers (masked — only the last 4 characters).

SERVERFramesail SOURCEhttps://api.framesail.com/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/com-framesail-framesail/list-provider-keys.md

WHAT IT DOES

What list_provider_keys does on Framesail

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

RISK

Why list_provider_keys is rated Low

This is a read-only query operation that retrieves metadata about registered key providers. The masking of keys further confirms this is a safe informational tool with no side effects. While it touches sensitive infrastructure (key management), the masked output and read-only nature keep severity low.

From the tool's definition Tool description states 'List registered BYOK providers (masked — only the last 4 characters)'. The verb 'list' and the fact that keys are masked indicate this retrieves configuration information without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_provider_keys safely

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

list_provider_keys Allowed

list_provider_keys 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": {
    "list_provider_keys": {}
  }
}

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

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

FAQ

Questions about list_provider_keys

What does the list_provider_keys tool do? +

List registered BYOK providers (masked — only the last 4 characters). It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_provider_keys? +

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

What risk level is list_provider_keys? +

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

Can I rate-limit list_provider_keys? +

Yes. Add a rate_limit block to the list_provider_keys 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 list_provider_keys completely? +

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

list_provider_keys is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Framesail, and thousands of servers like it.

This server

All 68 Framesail tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

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