Get a list of all authentication keys associated with a specific application.
AI agents call get_application_keys to retrieve information from Searchcraft MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves authentication keys without altering them. While the keys themselves are sensitive credentials, the tool merely queries and returns them (Read operation). The severity is low because the tool does not execute actions, modify data, delete resources, or move money. The risk lies in what an attacker does with the retrieved keys afterward, not in this tool's direct capability.
From the tool's definition Tool name 'get_application_keys' and description 'Get a list of all authentication keys associated with a specific application' indicate retrieval of existing data with no modification or deletion.
Documented attack patterns abuse exactly the kind of access get_application_keys gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Searchcraft MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_application_keys:
{
"version": "1",
"default": "deny",
"tools": {
"get_application_keys": {}
}
} get_application_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.
Get a list of all authentication keys associated with a specific application. It is categorised as a Read tool in the Searchcraft MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Searchcraft MCP Server MCP server in PolicyLayer and add a rule for get_application_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 Searchcraft MCP Server. Nothing to install.
get_application_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 get_application_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 get_application_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.
get_application_keys is provided by the Searchcraft MCP Server MCP server (searchcraft-inc/searchcraft-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Searchcraft 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.
48 Searchcraft MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.