Confirm that a media file was successfully uploaded to the presigned URL. Call this after uploading the file via HTTP PUT to the URL from social_api_get_media_upload_url. Once verified, the media_id can be included in social_api_create_post's media_ids array.
Part of the Mcp Socialapi server.
Free to start. No card required.
AI agents call social_api_verify_media_upload to retrieve information from Mcp Socialapi without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though social_api_verify_media_upload only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"social_api_verify_media_upload": {}
}
}See the full Mcp Socialapi policy for all 75 tools.
These attack patterns abuse exactly the kind of access social_api_verify_media_upload gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Confirm that a media file was successfully uploaded to the presigned URL. Call this after uploading the file via HTTP PUT to the URL from social_api_get_media_upload_url. Once verified, the media_id can be included in social_api_create_post's media_ids array.. It is categorised as a Read tool in the Mcp Socialapi MCP Server, which means it retrieves data without modifying state.
Register the Mcp Socialapi MCP server in PolicyLayer and add a rule for social_api_verify_media_upload: 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 Mcp Socialapi. Nothing to install.
social_api_verify_media_upload 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 social_api_verify_media_upload 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 social_api_verify_media_upload. 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.
social_api_verify_media_upload is provided by the Mcp Socialapi MCP server (mcp-socialapi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 75 Mcp Socialapi tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.