save_coop_event
PARTIAL SAVE: writes ONLY the 'CoopEvent' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Cooperative multi-player events — guild raids, server-wide goals, leaderboard tournaments where players contribute together. Distinct from TimedEvent (solo) and Leaderboard (pu...
This record as markdown: /tools/com-idosgames-platform/save-coop-event.md
What save_coop_event does on iDos Games
AI agents use save_coop_event to create or update resources in iDos Games, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your iDos Games environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
value | object | Yes | Root configuration of the title's cooperative events system. Plugs into TitlePublicConfigurationModel as CoopEvent. |
title_id | string | Yes | TitleID, для которого сохраняются данные. |
Parameters from the server's own tool schema.
Why save_coop_event is rated Medium
An AI agent can call save_coop_event faster than any human can review: one bad instruction and it creates or modifies resources in iDos Games by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs save_coop_event safely
PolicyLayer is an MCP gateway: it sits between your AI agents and iDos Games, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_coop_event, this is the rule to start with:
save_coop_event 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.
The button opens the PolicyLayer dashboard: create your workspace, connect iDos Games, apply this rule, and every save_coop_event call is checked against it from then on.
Questions about save_coop_event
PARTIAL SAVE: writes ONLY the 'CoopEvent' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Cooperative multi-player events — guild raids, server-wide goals, leaderboard tournaments where players contribute together. Distinct from TimedEvent (solo) and Leaderboard (pure ranking). Defines participation rules, shared progress, contribution tracking, and tiered rewards based on collective performance. It is categorised as a Write tool in the iDos Games MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
save_coop_event accepts 2 parameters: value, title_id. Required: value, title_id. The full parameter table on this page comes from the server's own tool schema.
Register the iDos Games MCP server in PolicyLayer and add a rule for save_coop_event: 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 iDos Games. Nothing to install.
save_coop_event 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 save_coop_event 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 save_coop_event. 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.
save_coop_event is provided by the iDos Games MCP server (https://site.idosgames.com/api/v2/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on iDos Games, and thousands of servers like it.
This server
Across the catalogue