Return the bearer token from the Authorization header of the MCP settings, which is used to debug.
AI agents call show_api_key to retrieve information from Jina AI Remote MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While technically a read operation (retrieves data without modification), this tool exposes API credentials that grant full access to Jina AI services and potentially authenticated resources. Unauthorized access to API keys enables attackers to impersonate legitimate users, consume quota, access restricted content, and pivot to other systems.
From the tool's definition Tool returns 'bearer token from the Authorization header' which is a sensitive credential used for API authentication.
Documented attack patterns abuse exactly the kind of access show_api_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jina AI Remote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for show_api_key:
{
"version": "1",
"default": "deny",
"tools": {
"show_api_key": {}
}
} show_api_key is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return the bearer token from the Authorization header of the MCP settings, which is used to debug. It is categorised as a Read tool in the Jina AI Remote MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Jina AI Remote MCP Server MCP server in PolicyLayer and add a rule for show_api_key: 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 Jina AI Remote MCP Server. Nothing to install.
show_api_key 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 show_api_key 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 show_api_key. 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.
show_api_key is provided by the Jina AI Remote MCP Server MCP server (jina-ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jina AI Remote MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Jina AI Remote MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.