libi.show_api_config

Open the inline API-key config panel for a bundled MCP (right of the chat). Call this the moment a tool fails with mcp_missing_key, or libi.list_bundled_mcps shows a needed MCP as needs_config, then tell the user which key to paste. Never read or echo the key value.

SERVERLibi SOURCENagellabs/libi

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/libi/libi.show-api-config.md

WHAT IT DOES

What libi.show_api_config does on Libi

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

RISK

Why libi.show_api_config is rated Low

Tool displays configuration UI for credentials without reading, modifying, or executing external operations.

From the tool's definition Open the inline API-key config panel; never read or echo the key value.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs libi.show_api_config safely

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

libi.show_api_config Allowed

libi.show_api_config 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": {
    "libi.show_api_config": {}
  }
}

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

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

FAQ

Questions about libi.show_api_config

What does the libi.show_api_config tool do? +

How do I enforce a policy on libi.show_api_config? +

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

What risk level is libi.show_api_config? +

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

Can I rate-limit libi.show_api_config? +

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

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

libi.show_api_config is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Libi, and thousands of servers like it.

This server

All 215 Libi tools →

Across the catalogue

The MCP Attack Database →

Guides

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