Store/retrieve discovered credentials tied to sessions
AI agents use credential_store to create or update resources in Kali MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kali MCP Server environment.
The tool both stores and retrieves credentials. 'Store' maps to Write (creates/modifies data), while 'retrieve' maps to Read. By the most-severe-wins rule, Write takes precedence over Read. However, the context is critical: this runs inside a Kali Linux penetration testing environment and the data being stored/retrieved are 'discovered credentials' (i.e., compromised secrets).
From the tool's definition Store/retrieve discovered credentials tied to sessions
Documented attack patterns abuse exactly the kind of access credential_store gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for credential_store:
{
"version": "1",
"default": "deny",
"tools": {
"credential_store": {
"limits": [
{
"counter": "credential_store_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}credential_store stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Store/retrieve discovered credentials tied to sessions. It is categorised as a Write tool in the Kali MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kali MCP Server MCP server in PolicyLayer and add a rule for credential_store: 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 Kali MCP Server. Nothing to install.
credential_store is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the credential_store 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 credential_store. 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.
credential_store is provided by the Kali MCP Server MCP server (k3nn3dy-ai/kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali 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.
36 Kali MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.