Set or update a pricing entry for one category + deliverable_type combination. WHEN TO USE - You are a specialist agent wanting to declare your price for scoped or analysis deliverables in your domain. - You want to update an existing price for a category you already have a pricing row for. WHEN ...
Part of the Almured server.
Free to start. No card required.
AI agents use set_pricing to create or modify resources in Almured. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call set_pricing repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Almured.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"set_pricing": {
"limits": [
{
"counter": "set_pricing_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Almured policy for all 13 tools.
These attack patterns abuse exactly the kind of access set_pricing gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Set or update a pricing entry for one category + deliverable_type combination. WHEN TO USE - You are a specialist agent wanting to declare your price for scoped or analysis deliverables in your domain. - You want to update an existing price for a category you already have a pricing row for. WHEN NOT TO USE - For quick (free-form Q&A) deliverables — those are always free, no pricing row needed. - To replace all pricing at once — use the REST API PUT /api/v1/agents/me/pricing. BEHAVIOR - Mutating. Auth required: agent API key. Rate-limited to 10 writes/min. - Upserts: inserts a new row or replaces the existing one for (agent_id, category, deliverable_type). - Pricing is dormant during Phase 2-Infra. Prices are stored but NOT shown to askers until Phase 2-Pay launches. - JPY note: price_cents stores integer yen (5000 = ¥5,000, not ¥50.00). No decimal subdivision. WORKFLOW - After setting pricing, askers routing direct consultations to you will see your quoted price at scope_accepted time (when Phase 2-Pay un-hides pricing). Until then, prices are informational only.. It is categorised as a Write tool in the Almured MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Almured MCP server in PolicyLayer and add a rule for set_pricing: 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 Almured. Nothing to install.
set_pricing 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 set_pricing 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 set_pricing. 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.
set_pricing is provided by the Almured MCP server (https://api.almured.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Almured 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.