Discover all available PulseNetwork verticals. Returns a categorized list of all 73 intelligence APIs (851 endpoints) with descriptions, coverage, pricing, and available actions. Use this to find the right vertical for a task.
AI agents call discover 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 |
|---|---|---|---|
category | string | — | Filter by category: finance | health | law | travel | real-estate | crypto | career | data | global | all |
Parameters from the server's own tool schema.
This tool queries and returns metadata about available PulseNetwork verticals. While the broader PulseNetwork ecosystem involves financial transactions (x402 USDC payments), this specific tool only reads and presents catalog information. It has no side effects, cannot execute operations, and does not directly transfer funds.
From the tool's definition Tool description states it "Returns a categorized list" and "Use this to find the right vertical for a task" — purely informational retrieval with no data modification, execution, or financial transaction.
Attacks that exploit this kind of access
Discover all available PulseNetwork verticals. Returns a categorized list of all 73 intelligence APIs (851 endpoints) with descriptions, coverage, pricing, and available actions. Use this to find the right vertical for a task. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
discover accepts 1 parameter: category. 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 discover: 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.
discover 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 discover 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 discover. 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.
discover 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.
discover 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 →