Get file metadata (size, modified time, etc).
AI agents call get_file_info to retrieve information from TermPipe MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns file metadata without creating, modifying, deleting, or executing anything. It has minimal security impact as an information retrieval operation. Even though the server provides terminal access broadly, this specific tool is scoped to non-destructive metadata queries.
From the tool's definition Tool name is 'get_file_info' and description states it retrieves file metadata (size, modified time, etc) with no modification or execution capability mentioned.
Attacks that exploit this kind of access
Get file metadata (size, modified time, etc). It is categorised as a Read tool in the TermPipe MCP MCP Server, which means it retrieves data without modifying state.
Register the TermPipe MCP server in PolicyLayer and add a rule for get_file_info: 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 TermPipe MCP. Nothing to install.
get_file_info 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 get_file_info 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 get_file_info. 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.
get_file_info is provided by the TermPipe MCP server (wbind-core/termpipe-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 →