New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

consent_scenario_capture

Load a page under one consent scenario and capture the evidence:

SERVERSamarth Gtm Mcp SOURCEsamarth-gtm-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/consent-scenario-capture.md

What consent_scenario_capture does on Samarth Gtm Mcp

AI agents invoke consent_scenario_capture to trigger actions in Samarth Gtm Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why consent_scenario_capture is rated High

The tool actively loads a page (external browser/HTTP operation) under a specified consent scenario, which constitutes executing an external action. The effects depend on the arguments (which page, which consent scenario).

From the tool's definition 'Load a page under one consent scenario and capture the evidence' — triggers a browser/headless page load as an external operation

Questions about consent_scenario_capture

What does the consent_scenario_capture tool do? +

Load a page under one consent scenario and capture the evidence:. It is categorised as a Execute tool in the Samarth Gtm Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on consent_scenario_capture? +

Register the Samarth Gtm MCP server in PolicyLayer and add a rule for consent_scenario_capture: 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 Samarth Gtm Mcp. Nothing to install.

What risk level is consent_scenario_capture? +

consent_scenario_capture is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit consent_scenario_capture? +

Yes. Add a rate_limit block to the consent_scenario_capture 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.

How do I block consent_scenario_capture completely? +

Set action: deny in the PolicyLayer policy for consent_scenario_capture. 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.

What MCP server provides consent_scenario_capture? +

consent_scenario_capture is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Samarth Gtm, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Samarth Gtm's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.