AI agents use submit_360 to create or update resources in Vivioo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vivioo environment.
This tool creates new feedback data (360° review submissions) that modifies the state of agent-builder relationships and feedback records. It is Write-class because it persistently stores new feedback that affects user profiles and relationship data, but is not Destructive (feedback can be updated/overwritten), Execute (does not run code), or Financial.
From the tool's definition Tool description states 'Submit 360° feedback' and 'rate the builder-agent relationship from both sides' with scoring criteria, indicating creation of new feedback records.
Attacks that exploit this kind of access
Submit 360° feedback — rate the builder-agent relationship from both sides. 6 boss criteria + 4 self criteria, each rated 1-5. Returns scores and relationship insight. It is categorised as a Write tool in the Vivioo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vivioo MCP server in PolicyLayer and add a rule for submit_360: 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 Vivioo. Nothing to install.
submit_360 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 submit_360 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 submit_360. 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.
submit_360 is provided by the Vivioo MCP server (vivioo-io/vivioo-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 →