archive_status
A write tool on the 23 Open Chat Reviewer MCP server.
This record as markdown: /tools/23-open-chat-reviewer/archive-status.md
What archive_status does on 23 Open Chat Reviewer
AI agents use archive_status to create or update resources in 23 Open Chat Reviewer, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 23 Open Chat Reviewer environment.
Why archive_status is rated Medium
An AI agent can call archive_status faster than any human can review: one bad instruction and it creates or modifies resources in 23 Open Chat Reviewer by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs archive_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 23 Open Chat Reviewer, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive_status, this is the rule to start with:
archive_status stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 23 Open Chat Reviewer, apply this rule, and every archive_status call is checked against it from then on.
Questions about archive_status
archive_status is a write tool on the 23 Open Chat Reviewer MCP server. It is categorised as a Write tool in the 23 Open Chat Reviewer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 23 Open Chat Reviewer MCP server in PolicyLayer and add a rule for archive_status: 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 23 Open Chat Reviewer. Nothing to install.
archive_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the archive_status 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 archive_status. 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.
archive_status is provided by the 23 Open Chat Reviewer MCP server (MiddleDistances/23-open-chat-reviewer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 23 Open Chat Reviewer, and thousands of servers like it.
This server
Across the catalogue