list_applied_redactions
AI agents call list_applied_redactions to retrieve information from PDF Redaction MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data about redactions without modifying, deleting, or executing operations. It fits the 'Read' category as it retrieves information about the state of the document. Severity is low because listing metadata about redactions poses minimal risk—it does not modify data, execute code, or cause irreversible changes.
From the tool's definition Tool name 'list_applied_redactions' indicates retrieval of information about redactions that have been applied. The verb 'list' is a query operation with no side effects.
Attacks that exploit this kind of access
list_applied_redactions. It is categorised as a Read tool in the PDF Redaction MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PDF Redaction MCP Server MCP server in PolicyLayer and add a rule for list_applied_redactions: 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 PDF Redaction MCP Server. Nothing to install.
list_applied_redactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_applied_redactions 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 list_applied_redactions. 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.
list_applied_redactions is provided by the PDF Redaction MCP Server MCP server (marc-hanheide/redact_mcp). 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 →