get_recent_work

A read tool on the 23 Open Chat Reviewer MCP server.

SERVER23 Open Chat Reviewer SOURCEMiddleDistances/23-open-chat-reviewer

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/23-open-chat-reviewer/get-recent-work.md

WHAT IT DOES

What get_recent_work does on 23 Open Chat Reviewer

AI agents call get_recent_work to retrieve information from 23 Open Chat Reviewer without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_recent_work is rated Low

Even though get_recent_work only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_recent_work 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 get_recent_work, this is the rule to start with:

get_recent_work Allowed

get_recent_work is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_recent_work": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 23 Open Chat Reviewer, apply this rule, and every get_recent_work call is checked against it from then on.

FAQ

Questions about get_recent_work

What does the get_recent_work tool do? +

get_recent_work is a read tool on the 23 Open Chat Reviewer MCP server. It is categorised as a Read tool in the 23 Open Chat Reviewer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recent_work? +

Register the 23 Open Chat Reviewer MCP server in PolicyLayer and add a rule for get_recent_work: 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.

What risk level is get_recent_work? +

get_recent_work is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_recent_work? +

Yes. Add a rate_limit block to the get_recent_work 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.

How do I block get_recent_work completely? +

Set action: deny in the PolicyLayer policy for get_recent_work. 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.

What MCP server provides get_recent_work? +

get_recent_work 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.

KEEP EXPLORING

More on 23 Open Chat Reviewer, and thousands of servers like it.

This server

All 5 23 Open Chat Reviewer tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →