place_media_on_site

Вставити завантажений файл (зображення) на конкретне місце сайту — замінює src у знайденому <img> тегу. Безпечна операція: checksum, lock, Undo-сумісний checkpoint. Використовуй замість update_portal_page коли потрібно замінити лише одне зображення.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp
Medium RISK CLASS
Category Write
Parameters 75 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/place-media-on-site.md

What place_media_on_site does on QuintaDB

AI agents use place_media_on_site to create or update resources in QuintaDB, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuintaDB environment.

ParameterTypeRequiredDescription
app_id string Yes Project ID (from list_projects)
page_id string Yes Portal page ID (from list_portal_pages)
media_id string Yes ID файлу з MyFile (з diamant_upload або media library)
portal_id string Yes Portal ID (from list_portals or describe_project)
current_src string Поточний src зображення для заміни (URL або відносний шлях)
css_selector string CSS-селектор для пошуку img-елемента (альтернатива current_src)
page_checksum string Yes SHA256 поточного HTML сторінки — береться з get_portal_page відповіді поля checksum. Обов'язково для захисту від паралельних змін.

Parameters from the server's own tool schema.

Why place_media_on_site is rated Medium

The tool modifies site content by replacing image sources, which is a write operation. While the description emphasizes safety features (checksum, lock, undo-compatibility), the fundamental operation is creating or modifying data (image placement on a site). It is not destructive since changes can be undone, not executable code, and not financial.

From the tool's definition Tool description states it 'inserts an uploaded file (image) on a specific site location — replaces src in a found <img> tag' and is described as 'Undo-compatible checkpoint'. This is a reversible modification of site content.

Questions about place_media_on_site

What does the place_media_on_site tool do? +

Вставити завантажений файл (зображення) на конкретне місце сайту — замінює src у знайденому <img> тегу. Безпечна операція: checksum, lock, Undo-сумісний checkpoint. Використовуй замість update_portal_page коли потрібно замінити лише одне зображення. It is categorised as a Write tool in the QuintaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does place_media_on_site accept? +

place_media_on_site accepts 7 parameters: app_id, page_id, media_id, portal_id, current_src, css_selector, page_checksum. Required: app_id, page_id, media_id, portal_id, page_checksum. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on place_media_on_site? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for place_media_on_site: 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 QuintaDB. Nothing to install.

What risk level is place_media_on_site? +

place_media_on_site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit place_media_on_site? +

Yes. Add a rate_limit block to the place_media_on_site 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.

How do I block place_media_on_site completely? +

Set action: deny in the PolicyLayer policy for place_media_on_site. 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.

What MCP server provides place_media_on_site? +

place_media_on_site is provided by the QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on QuintaDB, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of QuintaDB's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.