record_consent
Capture explicit, versioned, timestamped DPDP consent and ISSUE the consent_token that unlocks data-pull tools (also returns jti for revoke_consent). Call this BEFORE pull_bureau or fetch_bank_statements. IMPORTANT: only call with accepted=true AFTER the human has explicitly agreed in this conver...
This record as markdown: /tools/nitrostack/record-consent.md
What record_consent does on Nitrostack
AI agents use record_consent to create or update resources in Nitrostack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nitrostack environment.
Why record_consent is rated Medium
Creates a consent record and issues a token that unlocks sensitive data-pull tools.
From the tool's definition Capture explicit, versioned, timestamped DPDP consent and ISSUE the consent_token
Attacks that exploit this kind of access
The rule that runs record_consent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For record_consent, this is the rule to start with:
record_consent 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every record_consent call is checked against it from then on.
Questions about record_consent
Capture explicit, versioned, timestamped DPDP consent and ISSUE the consent_token that unlocks data-pull tools (also returns jti for revoke_consent). Call this BEFORE pull_bureau or fetch_bank_statements. IMPORTANT: only call with accepted=true AFTER the human has explicitly agreed in this conversation — never assume or pre-fill consent on their behalf. If accepted=false, no token is issued and those tools will refuse. It is categorised as a Write tool in the Nitrostack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nitrostack MCP server in PolicyLayer and add a rule for record_consent: 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 Nitrostack. Nothing to install.
record_consent 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 record_consent 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 record_consent. 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.
record_consent is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
This server
Across the catalogue