Send biometric signals from any sensor, get unified state back. Required: session_id + timestamp (ISO 8601) + at least one signal. Send whatever you have — the API fuses all signals into one state. Common signals (highest impact): - heart_rate (bpm, 30-220) + rmssd (ms) — cardiovascular - tone: c...
Risk signalsAccepts freeform code/query input (expression) · High parameter count (35 properties)
Part of the Nefesh — Real-Time Human State Awareness for AI server.
Free to start. No card required.
AI agents invoke ingest to trigger processes or run actions in Nefesh — Real-Time Human State Awareness for AI. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
ingest can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"ingest": {
"limits": [
{
"counter": "ingest_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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 ingest gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Send biometric signals from any sensor, get unified state back. Required: session_id + timestamp (ISO 8601) + at least one signal. Send whatever you have — the API fuses all signals into one state. Common signals (highest impact): - heart_rate (bpm, 30-220) + rmssd (ms) — cardiovascular - tone: calm | tense | anxious | hostile — vocal - sentiment: -1.0 to 1.0 — textual - expression: relaxed | neutral | tense — visual For trigger memory (cross-session psychological tracking): - Include subject_id (consistent per user, hashed) Returns same fields as get_human_state plus signals_received list and topics_detected (if conversation text was included). source_device is optional but improves confidence scoring. Not a medical device.. It is categorised as a Execute tool in the Nefesh — Real-Time Human State Awareness for AI MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nefesh — Real-Time Human State Awareness for AI MCP server in PolicyLayer and add a rule for ingest: 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.
ingest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ingest 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 ingest. 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.
ingest 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.