Low Risk

get_files_tracked

Get the list of tracked files.

How to control get_files_tracked ↓

AI agents call get_files_tracked to retrieve information from Archive Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns metadata about tracked files without modifying, deleting, or executing any operations. It is a straightforward read operation analogous to 'list' or 'get'. The low severity reflects minimal blast radius—an AI agent listing files cannot cause damage, though it may surface information about file organization.

From the tool's definition Tool name 'get_files_tracked' and description 'Get the list of tracked files' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_files_tracked gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Archive Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for get_files_tracked:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_files_tracked": {}
  }
}

get_files_tracked is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Archive Agent — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_files_tracked tool do? +

Get the list of tracked files. It is categorised as a Read tool in the Archive Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_files_tracked? +

Register the Archive Agent MCP server in PolicyLayer and add a rule for get_files_tracked: 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 Archive Agent. Nothing to install.

What risk level is get_files_tracked? +

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

Can I rate-limit get_files_tracked? +

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

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

get_files_tracked is provided by the Archive Agent MCP server (shredengineer/archive-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Archive Agent tool call.

Deterministic rules across all 7 Archive Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

7 Archive Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.