POST body must be in multipart/form-data format
AI agents use postmediamultipart to create or update resources in Revel Digital MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Revel Digital MCP Server environment.
The tool name 'postmediamultipart' combined with the multipart/form-data description indicates this uploads media content to the digital signage system. POST operations that create/upload content are Write category. Severity is medium as uploading unwanted or malicious media content could affect displays but is reversible (sibling delete tools exist).
From the tool's definition 'POST body must be in multipart/form-data format' — a POST operation uploading multipart data, typically used for file/media uploads
Attacks that exploit this kind of access
POST body must be in multipart/form-data format. It is categorised as a Write tool in the Revel Digital MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Revel Digital MCP Server MCP server in PolicyLayer and add a rule for postmediamultipart: 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 Revel Digital MCP Server. Nothing to install.
postmediamultipart 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 postmediamultipart 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 postmediamultipart. 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.
postmediamultipart is provided by the Revel Digital MCP Server MCP server (reveldigital/reveldigital-mcp-server). 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 →