list_recent_scans

List recent security scans

SERVERClaude MCP Server Ecosystem SOURCEcoder-rl/claude_mcpserver_dev1
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coder-rl-claude-mcpserver-dev1/list-recent-scans.md

What list_recent_scans does on Claude MCP Server Ecosystem

AI agents call list_recent_scans to retrieve information from Claude MCP Server Ecosystem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_recent_scans is rated Low

This tool performs a read-only query of security scan records. It has no side effects, does not execute code or commands, and does not modify or destroy data. The blast radius of misuse is minimal—an agent could potentially access metadata about past scans, but cannot trigger new scans or alter security posture. It clearly falls under the Read category.

From the tool's definition Tool name 'list_recent_scans' and description 'List recent security scans' indicate a retrieval operation that queries historical scan data without modifying, executing, or deleting anything.

Questions about list_recent_scans

What does the list_recent_scans tool do? +

List recent security scans. It is categorised as a Read tool in the Claude MCP Server Ecosystem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_recent_scans? +

Register the Claude MCP Server Ecosystem MCP server in PolicyLayer and add a rule for list_recent_scans: 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 Claude MCP Server Ecosystem. Nothing to install.

What risk level is list_recent_scans? +

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

Can I rate-limit list_recent_scans? +

Yes. Add a rate_limit block to the list_recent_scans 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 list_recent_scans completely? +

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

list_recent_scans is provided by the Claude MCP Server Ecosystem MCP server (coder-rl/claude_mcpserver_dev1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Claude MCP Server Ecosystem, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude MCP Server Ecosystem's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.