pullnexus_install
AI agents invoke pullnexus_install to trigger actions in PullNexus. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
An 'install' operation typically downloads and executes code or artifacts on the local system, which constitutes an Execute-level action. In the context of a CLI for AI resources (skills, tools, templates), installing a resource likely involves writing files and potentially executing setup scripts, making it at least Execute severity. Severity is high due to potential for arbitrary code execution on the host system.
From the tool's definition Tool name 'pullnexus_install' — the word 'install' implies executing an installation process that modifies the local system environment.
Documented attack patterns abuse exactly the kind of access pullnexus_install 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_install:
{
"version": "1",
"default": "deny",
"tools": {
"pullnexus_install": {
"limits": [
{
"counter": "pullnexus_install_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}pullnexus_install stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
pullnexus_install. It is categorised as a Execute tool in the PullNexus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PullNexus MCP server in PolicyLayer and add a rule for pullnexus_install: 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_install is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pullnexus_install 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_install. 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_install 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.