Find providers (organizations/individuals) in the PulseMCP registry. This tool can operate in two modes: 1. Find by ID: Retrieve a specific provider by its numeric ID - Returns a single provider with detailed information - Returns null if not found 2. Search by query: Search for providers by name...
AI agents call find_providers to retrieve information from Pulsemcp Cms Admin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval and search operations only. It queries the PulseMCP registry to find and return provider information without side effects. The dual-mode functionality (lookup by ID or search by criteria) are both read operations that do not modify, delete, or execute code. The low severity reflects minimal blast radius if misused—an AI agent could only retrieve existing provider data.
From the tool's definition Tool description states it can 'Retrieve a specific provider' and 'Search for providers' with returns of provider data. Actions are read-only queries: 'Find by ID' returns provider details, 'Search by query' searches and returns matching results.
Attacks that exploit this kind of access
Find providers (organizations/individuals) in the PulseMCP registry. This tool can operate in two modes: 1. Find by ID: Retrieve a specific provider by its numeric ID - Returns a single provider with detailed information - Returns null if not found 2. Search by query: Search for providers by name, URL, or slug - Searches across provider name, URL, and slug fields (case-insensitive) - Returns a list of matching providers with pagination support - Each result includes implementation counts Provider information includes: - ID and slug - Name and URL - Number of associated implementations - Creation and update timestamps Use cases: - Look up a specific provider by ID - Search for providers by name (e.g.,. It is categorised as a Read tool in the Pulsemcp Cms Admin MCP Server, which means it retrieves data without modifying state.
Register the Pulsemcp Cms Admin MCP server in PolicyLayer and add a rule for find_providers: 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.
find_providers 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 find_providers 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 find_providers. 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.
find_providers 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 →