Edit composition metadata using HTTP API
AI agents use edit-composition-metadata to create or update resources in EuConquisto Composer MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EuConquisto Composer MCP environment.
This tool performs reversible modification of data—editing metadata does not delete or irreversibly destroy content, nor does it execute arbitrary code or trigger external operations. It fits the Write category (creates or modifies data reversibly).
From the tool's definition Tool name 'edit-composition-metadata' combined with description 'Edit composition metadata using HTTP API' indicates modification of existing educational content metadata.
Attacks that exploit this kind of access
Edit composition metadata using HTTP API. It is categorised as a Write tool in the EuConquisto Composer MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EuConquisto Composer MCP server in PolicyLayer and add a rule for edit-composition-metadata: 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 EuConquisto Composer MCP. Nothing to install.
edit-composition-metadata 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 edit-composition-metadata 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 edit-composition-metadata. 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.
edit-composition-metadata is provided by the EuConquisto Composer MCP server (rkm097git/euconquisto-composer-mcp-poc). 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 →