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

get_instance_operator_manual

Read the operator manual for a subscribed instance — caller-facing notes about HOW this instance is meant to be driven (not an instruction to the agent). Returns { manual, rules, context }:

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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

What get_instance_operator_manual does on ProAgentStore

AI agents call get_instance_operator_manual to retrieve information from ProAgentStore without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_instance_operator_manual is rated Low

Tool retrieves documentation and configuration notes without modifying or executing operations.

From the tool's definition Read the operator manual for a subscribed instance — caller-facing notes

Questions about get_instance_operator_manual

What does the get_instance_operator_manual tool do? +

Read the operator manual for a subscribed instance — caller-facing notes about HOW this instance is meant to be driven (not an instruction to the agent). Returns { manual, rules, context }:. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_instance_operator_manual? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for get_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 get_instance_operator_manual? +

get_instance_operator_manual is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_instance_operator_manual? +

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

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

get_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.