AI agents use set_publish_settings to create or update resources in VaultAssist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultAssist environment.
This tool modifies form metadata and access settings (publish configuration) in Google Forms, which is a reversible change. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve information (Read).
From the tool's definition Tool name 'set_publish_settings' and description 'Update the publish settings of a Google Form' indicate modification of form configuration. The verb 'Update' is characteristic of Write operations.
Documented attack patterns abuse exactly the kind of access set_publish_settings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for set_publish_settings:
{
"version": "1",
"default": "deny",
"tools": {
"set_publish_settings": {
"limits": [
{
"counter": "set_publish_settings_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_publish_settings 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.
Free to start. No card required.
Update the publish settings of a Google Form. It is categorised as a Write tool in the VaultAssist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VaultAssist MCP server in PolicyLayer and add a rule for set_publish_settings: 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 VaultAssist. Nothing to install.
set_publish_settings 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_publish_settings 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_publish_settings. 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_publish_settings is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.