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

update_backup_schedule

Update a Firestore backup schedule.

SERVERMcp SOURCEhttps://firestore.googleapis.com/mcp
Medium RISK CLASS
Category Write
Parameters 21 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-firestore-mcp/update-backup-schedule.md

What update_backup_schedule does on Mcp

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

ParameterTypeRequiredDescription
updateMask string The list of fields to be updated.
backupSchedule object Yes Required. The backup schedule to update.

Parameters from the server's own tool schema.

Why update_backup_schedule is rated Medium

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

Questions about update_backup_schedule

What does the update_backup_schedule tool do? +

Update a Firestore backup schedule. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_backup_schedule accept? +

update_backup_schedule accepts 2 parameters: updateMask, backupSchedule. Required: backupSchedule. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_backup_schedule? +

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

What risk level is update_backup_schedule? +

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

Can I rate-limit update_backup_schedule? +

Yes. Add a rate_limit block to the update_backup_schedule 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 update_backup_schedule completely? +

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

update_backup_schedule is provided by the MCP server (https://firestore.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on , and thousands of servers like it.

This server

// 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 '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.