marketplace_publish
AI agents use marketplace_publish to create or update resources in Loreto — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Loreto environment.
The tool creates or modifies marketplace content (publishing a skill listing), which is reversible—listings can typically be unpublished or deleted. This is a Write operation rather than Destructive because publishing is not irreversible.
From the tool's definition Tool name 'marketplace_publish' combined with server context showing a skills marketplace, along with sibling tools 'marketplace_my_listings' and 'marketplace_purchase', indicates this tool creates or publishes new marketplace listings.
Documented attack patterns abuse exactly the kind of access marketplace_publish gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Loreto, and nothing reaches the server without passing your rules. This is the rule we recommend for marketplace_publish:
{
"version": "1",
"default": "deny",
"tools": {
"marketplace_publish": {
"limits": [
{
"counter": "marketplace_publish_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}marketplace_publish stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
marketplace_publish. It is categorised as a Write tool in the Loreto MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Loreto MCP server in PolicyLayer and add a rule for marketplace_publish: 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 Loreto. Nothing to install.
marketplace_publish 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 marketplace_publish 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 marketplace_publish. 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.
marketplace_publish is provided by the Loreto MCP server (kopias/loreto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Loreto, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Loreto tools catalogued and risk-classified — across an index of 43,000+ MCP servers.