Update the Published Tier (col AE) for a metro after weekly review. AE is the investor-facing tier that overrides col E in all server responses. This does NOT change col E (Status) — E drives monitoring and is only changed by db_corrections scripts. Side effects: if AF (Stale Progress) is flagged...
Part of the Cap Rate Signals server.
Free to start. No card required.
AI agents use set_published_tier to create or modify resources in Cap Rate Signals. 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_published_tier 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 Cap Rate Signals.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"set_published_tier": {
"limits": [
{
"counter": "set_published_tier_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Cap Rate Signals policy for all 14 tools.
These attack patterns abuse exactly the kind of access set_published_tier 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.
Update the Published Tier (col AE) for a metro after weekly review. AE is the investor-facing tier that overrides col E in all server responses. This does NOT change col E (Status) — E drives monitoring and is only changed by db_corrections scripts. Side effects: if AF (Stale Progress) is flagged, it is cleared automatically. If AG (Proposed Tier) matches the tier being set, AG is cleared too. Use this when you agree with a stale-flag demotion or a tier proposal. Trigger phrases: 'set published tier for X to NOW', 'promote X to NEXT', 'accept the tier proposal for X', 'demote X to LATER', 'update AE for X'. It is categorised as a Write tool in the Cap Rate Signals MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cap Rate Signals MCP server in PolicyLayer and add a rule for set_published_tier: 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 Cap Rate Signals. Nothing to install.
set_published_tier 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_published_tier 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_published_tier. 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_published_tier is provided by the Cap Rate Signals MCP server (capratesignals/cap-rate-signals). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Cap Rate Signals 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.