New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

silos_updateInstance

Rename a database instance (PATCH /v1/silos/instances/{instance_id})

SERVERGenesis SOURCE@onesi/genesis-mcp
Medium RISK CLASS
Category Write
Parameters 22 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/onesi-genesis-mcp/silos-updateinstance.md

What silos_updateInstance does on Genesis

AI agents use silos_updateInstance to create or update resources in Genesis, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Genesis environment.

ParameterTypeRequiredDescription
body object Yes
instance_id string Yes

Parameters from the server's own tool schema.

Why silos_updateInstance is rated Medium

An AI agent can call silos_updateInstance faster than any human can review: one bad instruction and it creates or modifies resources in Genesis by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (body)

Questions about silos_updateInstance

What does the silos_updateInstance tool do? +

Rename a database instance (PATCH /v1/silos/instances/{instance_id}). It is categorised as a Write tool in the Genesis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does silos_updateInstance accept? +

silos_updateInstance accepts 2 parameters: body, instance_id. Required: body, instance_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on silos_updateInstance? +

Register the Genesis MCP server in PolicyLayer and add a rule for silos_updateInstance: 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 Genesis. Nothing to install.

What risk level is silos_updateInstance? +

silos_updateInstance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit silos_updateInstance? +

Yes. Add a rate_limit block to the silos_updateInstance 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.

How do I block silos_updateInstance completely? +

Set action: deny in the PolicyLayer policy for silos_updateInstance. 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.

What MCP server provides silos_updateInstance? +

silos_updateInstance is provided by the Genesis MCP server (@onesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Genesis, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Genesis's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.