AI agents call pullnexus_search to retrieve information from PullNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations are Read-category tools—they retrieve information without modifying, executing, or deleting data. Despite the empty description lowering confidence slightly, the tool name and server's stated functionality (search capabilities) make Read the appropriate classification. Severity is low because searching a registry poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'pullnexus_search' and server context ('Search, pull, and submit reusable skills') indicate this is a search/query function. No description provided, but naming and server purpose strongly suggest data retrieval without side effects.
Documented attack patterns abuse exactly the kind of access pullnexus_search gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PullNexus, and nothing reaches the server without passing your rules. This is the rule we recommend for pullnexus_search:
{
"version": "1",
"default": "deny",
"tools": {
"pullnexus_search": {}
}
}pullnexus_search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
pullnexus_search. It is categorised as a Read tool in the PullNexus MCP Server, which means it retrieves data without modifying state.
Register the PullNexus MCP server in PolicyLayer and add a rule for pullnexus_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 PullNexus. Nothing to install.
pullnexus_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 pullnexus_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 pullnexus_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.
pullnexus_search is provided by the PullNexus MCP server (mrwillist/pullnexus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PullNexus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 PullNexus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.