Create a new item in Omeka S.
AI agents use create-item to create or update resources in Omeka S Mcp Sample — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Omeka S Mcp Sample environment.
Creating items in Omeka S (a digital library/museum platform) adds new records to the system. This is a Write operation because it creates data that can be modified or deleted later, unlike Destructive operations. Severity is medium because uncontrolled item creation could clutter the database or create unwanted catalog entries, but the impact is limited to the digital collection and reversible.
From the tool's definition Tool name 'create-item' and description 'Create a new item in Omeka S' indicate data creation. This is a reversible modification operation.
Attacks that exploit this kind of access
Create a new item in Omeka S. It is categorised as a Write tool in the Omeka S Mcp Sample MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Omeka S Mcp Sample MCP server in PolicyLayer and add a rule for create-item: 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 Omeka S Mcp Sample. Nothing to install.
create-item 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-item 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-item. 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-item is provided by the Omeka S Mcp Sample MCP server (nakamura196/omeka-s-mcp-sample). 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 →