Request a free Nefesh API key. No existing API key needed for this call. IMPORTANT: You MUST ask the user for their real email address before calling this tool. Do NOT invent, guess, or generate an email address. The user will receive a verification link they must click to activate the key. Witho...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Nefesh — Real-Time Human State Awareness for AI server.
Free to start. No card required.
AI agents call request_api_key to retrieve information from Nefesh — Real-Time Human State Awareness for AI without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though request_api_key only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"request_api_key": {}
}
}See the full Nefesh — Real-Time Human State Awareness for AI policy for all 6 tools.
These attack patterns abuse exactly the kind of access request_api_key gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Request a free Nefesh API key. No existing API key needed for this call. IMPORTANT: You MUST ask the user for their real email address before calling this tool. Do NOT invent, guess, or generate an email address. The user will receive a verification link they must click to activate the key. Without clicking that link, no API key will be issued. Disposable or temporary email services are blocked. Example prompt to the user: "What is your email address? You will receive a verification link to activate your free API key." Flow: call this with the user's real email, then poll check_api_key_status every 10 seconds until status is 'ready'. Free tier: 1,000 calls/month, all signal types, 10 req/min. No credit card.. It is categorised as a Read tool in the Nefesh — Real-Time Human State Awareness for AI MCP Server, which means it retrieves data without modifying state.
Register the Nefesh — Real-Time Human State Awareness for AI MCP server in PolicyLayer and add a rule for request_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 Nefesh — Real-Time Human State Awareness for AI. Nothing to install.
request_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 request_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 request_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.
request_api_key is provided by the Nefesh — Real-Time Human State Awareness for AI MCP server (https://mcp.nefesh.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Nefesh — Real-Time Human State Awareness for AI tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.