archivebox_core
AI agents invoke archivebox_core to trigger actions in ArchiveBox API. 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.
The server description indicates the server supports executing CLI commands and managing archives. A 'core' tool on such a server likely exposes broad functionality including execution of CLI commands and write/destructive operations.
From the tool's definition Tool name: archivebox_core; description is empty. Server description mentions 'executing CLI commands' and 'adding URLs to archives, managing snapshots' — core functionality likely encompasses these capabilities.
Attacks that exploit this kind of access
archivebox_core. It is categorised as a Execute tool in the ArchiveBox API MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ArchiveBox API MCP server in PolicyLayer and add a rule for archivebox_core: 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 ArchiveBox API. Nothing to install.
archivebox_core 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 archivebox_core 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 archivebox_core. 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.
archivebox_core is provided by the ArchiveBox API MCP server (knuckles-team/archivebox-api). 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 →