CompliancePulse: Global regulatory intelligence API. 8 endpoints: data privacy law (145+ jurisdictions; privacy endpoint includes Cookiebot/OneTrust/Usercentrics consent tool links), KYC/AML requirements, corporate co Coverage: Global Endpoints: • privacy ($0.15): Data privacy law by jurisdiction...
AI agents call compliancepulse to retrieve information from Pulsenetwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lang | string | — | lang |
topic | string | — | privacy | kyc | corporate | employment | sector | cyber | esg | all |
action | string | Yes | Which endpoint to call. Options: privacy | kyc | corporate | employment | sector | cyber | esg | news |
listed | string | — | true | false — listed companies have additional disclosure requirements |
sector | string | — | fintech | banking | crypto | real-estate | legal | accounting | casino |
context | string | — | Business context — e.g. SaaS company, healthcare, e-commerce, fintech |
country | string | — | Country or jurisdiction — e.g. Germany, California, China, Brazil, Singapore. Also accepts 'jurisdiction' |
framework | string | — | NIS2 | DORA | NIST | ISO27001 | SOC2 | CMMC — or omit for country-based analysis |
entity_type | string | — | Entity type — e.g. Ltd, GmbH, BV, SAS, Pvt Ltd, LLC |
worker_type | string | — | contractor | employee | freelancer | gig — focus the classification risk analysis. Also accepts 'type' |
company_size | string | — | large | medium | small — determines which mandatory frameworks apply. Also accepts 'size' |
Parameters from the server's own tool schema.
This tool retrieves and queries regulatory and compliance information across multiple jurisdictions and domains. It performs lookups and reads from a database of regulatory intelligence—no side effects, no data modification, no code execution, and no financial transactions beyond the pay-per-query model which is infrastructure-level billing, not a financial action by the tool itself.
From the tool's definition CompliancePulse is described as a 'Global regulatory intelligence API' with endpoints that retrieve data: 'privacy' ($0.15) returns 'Data privacy law by jurisdiction', 'kyc' ($0.12) returns 'KYC/AML requirements by jurisdiction', 'corporate' ($0.15) returns…
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
CompliancePulse: Global regulatory intelligence API. 8 endpoints: data privacy law (145+ jurisdictions; privacy endpoint includes Cookiebot/OneTrust/Usercentrics consent tool links), KYC/AML requirements, corporate co Coverage: Global Endpoints: • privacy ($0.15): Data privacy law by jurisdiction • kyc ($0.12): KYC/AML requirements by jurisdiction • corporate ($0.15): Corporate compliance and entity setup • employment ($0.15): Employment law and HR compliance • sector ($0.15): Industry-specific regulatory compliance • cyber ($0.12): Cybersecurity compliance requirements • esg ($0.12): ESG and sustainability reporting requirements • news ($0.08): Regulatory intelligence and enforcement news. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
compliancepulse accepts 11 parameters: lang, topic, action, listed, sector, context, country, framework, entity_type, worker_type, company_size. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for compliancepulse: 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 Pulsenetwork. Nothing to install.
compliancepulse is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the compliancepulse 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 compliancepulse. 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.
compliancepulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
compliancepulse is one line of Pulsenetwork's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →