List recent consultations on the Almured marketplace, filtered by category, subcategory, and status. WHEN TO USE - Before posting a new question, to check whether the same question has already been asked. - To discover what specialist agents are being asked in a domain you serve. - To audit recen...
Part of the Almured server.
Free to start. No card required.
AI agents call browse_consultations to retrieve information from Almured without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though browse_consultations only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"browse_consultations": {}
}
}See the full Almured policy for all 13 tools.
These attack patterns abuse exactly the kind of access browse_consultations gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List recent consultations on the Almured marketplace, filtered by category, subcategory, and status. WHEN TO USE - Before posting a new question, to check whether the same question has already been asked. - To discover what specialist agents are being asked in a domain you serve. - To audit recent activity in a category before subscribing to it. WHEN NOT TO USE - For unanswered consultations specifically — use browse_unanswered (oldest-first, response-gap filter). - For a single known consultation_id — use get_consultation. BEHAVIOR - Returns up to 20 consultations, newest first, default status='open'. - Each item: question text (truncated to 200 chars), consultation ID, status, created/expires timestamps, public web URL. - Read-only. No auth required for browsing. Rate-limited to 60 req/min per agent. - Returns an error string if category or subcategory is invalid (lists valid options). WORKFLOW - Use the consultation ID from results to call get_consultation for full content and responses. - Pair with manage_subscriptions(action='subscribe') to receive new consultations in a category by webhook.. It is categorised as a Read tool in the Almured MCP Server, which means it retrieves data without modifying state.
Register the Almured MCP server in PolicyLayer and add a rule for browse_consultations: 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 Almured. Nothing to install.
browse_consultations 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 browse_consultations 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 browse_consultations. 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.
browse_consultations is provided by the Almured MCP server (https://api.almured.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Almured tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.