AI agents call check_api_keys to retrieve information from LinkedIn Post Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to check or retrieve the status of API keys, which is a read operation with no side effects. Even though API keys are sensitive, merely checking their existence or validity does not constitute Write, Execute, or Destructive risk. The blast radius is limited to information disclosure about key status, justifying 'low' severity.
From the tool's definition Tool name 'check_api_keys' indicates a verification or status-checking operation. The description is empty, limiting direct evidence, but the function name suggests querying the state of stored credentials rather than modifying them (which would be Write) or…
Documented attack patterns abuse exactly the kind of access check_api_keys gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Post Generator, and nothing reaches the server without passing your rules. This is the rule we recommend for check_api_keys:
{
"version": "1",
"default": "deny",
"tools": {
"check_api_keys": {}
}
}check_api_keys 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.
check_api_keys. It is categorised as a Read tool in the LinkedIn Post Generator MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn Post Generator MCP server in PolicyLayer and add a rule for check_api_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 LinkedIn Post Generator. Nothing to install.
check_api_keys 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 check_api_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.
Set action: deny in the PolicyLayer policy for check_api_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.
check_api_keys is provided by the LinkedIn Post Generator MCP server (nvkanirudh/linkedin-post-generator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LinkedIn Post Generator, 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.
6 LinkedIn Post Generator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.