🔗 创建符号链接。自动创建父目录。链接名已存在时自动加后缀。
AI agents use file_symlink to create or update resources in Android MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Android MCP Server environment.
This tool creates symbolic links on the Android filesystem. It modifies the filesystem by creating new symlink entries and potentially new directories, which is a Write operation. Symlinks can be misused to redirect file access (e.g., pointing to sensitive files), elevating severity to medium. It does not irreversibly delete data, so Destructive does not apply.
From the tool's definition 创建符号链接 (create symbolic link); 自动创建父目录 (automatically creates parent directories); 链接名已存在时自动加后缀 (auto-suffix when link name exists)
Attacks that exploit this kind of access
🔗 创建符号链接。自动创建父目录。链接名已存在时自动加后缀。. It is categorised as a Write tool in the Android MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Android MCP Server MCP server in PolicyLayer and add a rule for file_symlink: 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 Android MCP Server. Nothing to install.
file_symlink is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the file_symlink 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 file_symlink. 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.
file_symlink is provided by the Android MCP Server MCP server (wujie272/android-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 →