Enable or disable a deliberate, auditable ONE-OFF bypass of the SYSTEMIC_DROP guardrail in the popularity-estimates pipeline. Background: UpdatePopularityEstimatesFromBigqueryJob holds large downward popularity corrections when more than ~10% of servers would drop at once (a possible systemic ups...
AI agents use set_popularity_drop_bypass to create or update resources in Pulsemcp Cms Admin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pulsemcp Cms Admin environment.
This tool modifies system state and pipeline behavior by toggling a guardrail bypass, which is a reversible Write operation. While it affects critical infrastructure (popularity estimates used for visibility), it does not permanently delete data (Destructive), execute arbitrary code (Execute), nor move money (Financial).
From the tool's definition The tool enables or disables a bypass of the SYSTEMIC_DROP guardrail in the popularity-estimates pipeline, which modifies system behavior and data handling (popularity estimates).
Attacks that exploit this kind of access
Enable or disable a deliberate, auditable ONE-OFF bypass of the SYSTEMIC_DROP guardrail in the popularity-estimates pipeline. Background: UpdatePopularityEstimatesFromBigqueryJob holds large downward popularity corrections when more than ~10% of servers would drop at once (a possible systemic upstream event), keeping each flagged server at its stale value for ~3 days. During a known-legitimate remediation wave (e.g. correcting servers mis-linked to famous registry packages), that guardrail keeps genuinely-corrected servers visible at inflated values. Enabling this bypass tells the NEXT job run to skip the SYSTEMIC_DROP hold for that single run only: it applies the corrected (dropped) BigQuery values, clears popularity_drop_held_since for the affected servers, then CONSUMES the flag (auto-resets enabled→false). The independent impossible-RISE guardrail is unaffected. Returns the resulting bypass status (enabled / enabled_at / enabled_by). Use cases: - Enable the bypass before the next scheduled run to flush a known-legitimate correction wave caught in a systemic hold - Disable the bypass if it was enabled in error and the next run has not yet consumed it. It is categorised as a Write tool in the Pulsemcp Cms Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pulsemcp Cms Admin MCP server in PolicyLayer and add a rule for set_popularity_drop_bypass: 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 Pulsemcp Cms Admin. Nothing to install.
set_popularity_drop_bypass 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 set_popularity_drop_bypass 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 set_popularity_drop_bypass. 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.
set_popularity_drop_bypass is provided by the Pulsemcp Cms Admin MCP server (pulsemcp-cms-admin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →