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 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read operation (retrieves data), but the data retrieved is a bearer token—a sensitive secret that grants authenticated access to the Jina API. Exposure of this credential could allow an attacker to impersonate the legitimate user, access their search history, consume their API quota, and potentially abuse their Jina account.
From the tool's definition Tool description explicitly states 'Return the bearer token from the Authorization header' — it retrieves and exposes a sensitive authentication credential used for API access.
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, 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 MCP Server, which means it retrieves data without modifying state.
Register the Jina AI 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. 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 MCP server (jina). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jina AI, 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 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.