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

add_instance_knowledge

Add user-specific knowledge to your private subscribed instance. This does not alter the creator

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/add-instance-knowledge.md

What add_instance_knowledge does on ProAgentStore

AI agents use add_instance_knowledge 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 add_instance_knowledge is rated Medium

The tool creates or modifies knowledge data within a user's private instance. This is a reversible Write operation (knowledge can be updated or removed), not destructive. The scope is limited to the user's own instance, mitigating blast radius.

From the tool's definition Tool name 'add_instance_knowledge' and description 'Add user-specific knowledge to your private subscribed instance' indicate creation/modification of data on the instance.

Questions about add_instance_knowledge

What does the add_instance_knowledge tool do? +

Add user-specific knowledge to your private subscribed instance. This does not alter the creator. 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 add_instance_knowledge? +

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

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

Can I rate-limit add_instance_knowledge? +

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

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

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