set_co_cal
AI agents use set_co_cal to create or update resources in Mipiti MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mipiti MCP Server environment.
Based on the naming pattern and context within the Mipiti security posture platform, this tool likely sets or updates a configuration value (possibly 'co-cal' for control or compliance calibration). The verb 'set' indicates modification of state. While the empty description limits certainty, the surrounding tools all perform reversible data modifications (Write category).
From the tool's definition Tool name 'set_co_cal' and context of sibling tools (add_asset, add_assumption, add_evidence, add_model_to_system) that all create or modify data. The 'set_' prefix indicates a write/update operation. Description is empty, reducing confidence.
Attacks that exploit this kind of access
set_co_cal. It is categorised as a Write tool in the Mipiti MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for set_co_cal: 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 Mipiti MCP Server. Nothing to install.
set_co_cal 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_co_cal 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_co_cal. 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_co_cal is provided by the Mipiti MCP Server MCP server (mipiti/mipiti-mcp). 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 →