Read a file the user uploaded and echo it back as a downloadable reference.
AI agents call inspect-file to retrieve information from Skybridge Everything App without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
file | object | Yes | |
user_intent | string | — | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used t |
Parameters from the server's own tool schema.
This tool retrieves and returns file content without modifying, deleting, or executing anything. It has no side effects beyond data retrieval. The blast radius of misuse is minimal—worst case an AI agent could read files the user intended to keep private, but no data is altered or destroyed. Severity is low because the user has already uploaded the file, implying consent to its inspection.
From the tool's definition Tool description states 'Read a file the user uploaded and echo it back as a downloadable reference.' The verb 'read' and the operation of retrieving and returning file contents are characteristic of Read category tools.
Risk signalsAccepts file system path (file)
Attacks that exploit this kind of access
Read a file the user uploaded and echo it back as a downloadable reference. It is categorised as a Read tool in the Skybridge Everything App MCP Server, which means it retrieves data without modifying state.
inspect-file accepts 2 parameters: file, user_intent. Required: file. The full parameter table on this page comes from the server's own tool schema.
Register the Skybridge Everything App MCP server in PolicyLayer and add a rule for inspect-file: 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 Skybridge Everything App. Nothing to install.
inspect-file 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 inspect-file 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 inspect-file. 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.
inspect-file is provided by the Skybridge Everything App MCP server (https://everything.skybridge.tech). 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 →