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) — cardio...
Accepts freeform code/query input (expression); High parameter count (35 properties)
Part of the Human State MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke ingest to trigger processes or run actions in Human State. 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. Intercept 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.
tools:
ingest:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Human State policy for all 6 tools.
Agents calling execute-class tools like ingest have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
ingest is one of the high-risk operations in Human State. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
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 Human State MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for ingest. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Human State MCP server.
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 Intercept 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 Intercept 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 Human State MCP server (nefesh-ai/human-state). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept