List_For_User_History

List history for specific user.

SERVERFiles Com SOURCEfiles-com-mcp

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/com-files-python-mcp/list-for-user-history.md

WHAT IT DOES

What List_For_User_History does on Files Com

AI agents call List_For_User_History to retrieve information from Files Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why List_For_User_History is rated Low

This tool queries and retrieves historical records for a user without creating, modifying, deleting, or executing operations. It is a read-only operation with minimal blast radius if misused by an LLM agent (data exposure is limited to audit logs or user activity history already accessible within the authorization context).

From the tool's definition Tool name contains 'List' and description states 'List history for specific user' — a retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs List_For_User_History safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For List_For_User_History, this is the rule to start with:

List_For_User_History Allowed

List_For_User_History 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": {
    "List_For_User_History": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Files Com, apply this rule, and every List_For_User_History call is checked against it from then on.

FAQ

Questions about List_For_User_History

What does the List_For_User_History tool do? +

List history for specific user. It is categorised as a Read tool in the Files Com MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on List_For_User_History? +

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

What risk level is List_For_User_History? +

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

Can I rate-limit List_For_User_History? +

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

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

List_For_User_History is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Files Com, and thousands of servers like it.

This server

All 68 Files Com tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

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