The social demand engine for your agent. Searches Reddit, X, YouTube, LinkedIn, and Bluesky in parallel for posts where people are expressing demand for what you described. Returns scored results ranked Hot / Warm / Cold by buying intent and recency. Filter by source and by time. Pricing: one cre...
AI agents call search to retrieve information from Gorilla MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and filters existing public posts from social media platforms. While it has a credit-based pricing model, the credits are consumed as a natural meter of service usage (like API call quotas), not a financial transaction that moves money or commits obligations in the Financial category sense.
From the tool's definition Tool description explicitly states it 'Searches' multiple social media platforms and 'Returns scored results' — core read operations that query and retrieve data without modification.
Attacks that exploit this kind of access
The social demand engine for your agent. Searches Reddit, X, YouTube, LinkedIn, and Bluesky in parallel for posts where people are expressing demand for what you described. Returns scored results ranked Hot / Warm / Cold by buying intent and recency. Filter by source and by time. Pricing: one credit per qualified lead (Hot or Warm); Cold results are free, and a failed search is fully refunded. LinkedIn is a paid-plan source; the free tier covers Reddit, X, YouTube, and Bluesky. Takes 30-90s. It is categorised as a Read tool in the Gorilla MCP MCP Server, which means it retrieves data without modifying state.
Register the Gorilla MCP server in PolicyLayer and add a rule for search: 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 Gorilla MCP. Nothing to install.
search 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 search 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 search. 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.
search is provided by the Gorilla MCP server (opusforge/gorilla-mcp). 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 →