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

set_instance_operator_manual

Replace the operator manual for a subscribed instance (max 16000 chars). The manual is caller-facing guidance — notes for the human or MCP client driving this instance. It is NOT injected as an agent instruction; it is fenced as data when the agent reads it via read_operator_manual. To write the ...

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/set-instance-operator-manual.md

What set_instance_operator_manual does on ProAgentStore

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

Why set_instance_operator_manual is rated Medium

Modifies operator manual data for an instance; reversible change without destructive or financial impact.

From the tool's definition Replace the operator manual for a subscribed instance

Questions about set_instance_operator_manual

What does the set_instance_operator_manual tool do? +

Replace the operator manual for a subscribed instance (max 16000 chars). The manual is caller-facing guidance — notes for the human or MCP client driving this instance. It is NOT injected as an agent instruction; it is fenced as data when the agent reads it via read_operator_manual. To write the agent. It is categorised as a Write tool in the ProAgentStore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_instance_operator_manual? +

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

What risk level is set_instance_operator_manual? +

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

Can I rate-limit set_instance_operator_manual? +

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

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

set_instance_operator_manual is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ProAgentStore, and thousands of servers like it.

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