Create a file download request to get a download URL.
AI agents use create_file_download_request to create or update resources in Buildium MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Buildium MCP Server environment.
The tool creates a file download request artifact, which is a reversible write operation. While it facilitates access to files, the core action is generating/creating a download request object rather than directly retrieving data.
From the tool's definition Tool name contains 'create_file_download_request' which creates a new resource (a download request), and the description states it creates a download request to obtain a URL. This is a reversible write operation that generates a new entity.
Attacks that exploit this kind of access
Create a file download request to get a download URL. It is categorised as a Write tool in the Buildium MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Buildium MCP Server MCP server in PolicyLayer and add a rule for create_file_download_request: 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 Buildium MCP Server. Nothing to install.
create_file_download_request 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 create_file_download_request 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 create_file_download_request. 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.
create_file_download_request is provided by the Buildium MCP Server MCP server (luthersystems/mcp-server-buildium). 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 →