list_instance_knowledge
List user-specific knowledge documents in your private subscribed instance.
This record as markdown: /tools/io-github-proagentstore-platform/list-instance-knowledge.md
What list_instance_knowledge does on ProAgentStore
AI agents call list_instance_knowledge 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 list_instance_knowledge is rated Low
This tool performs a read-only operation to retrieve and display knowledge documents. It does not create, modify, delete, or execute any actions—it simply lists existing data. The term 'List' is a classic Read operation pattern. The severity is low because unauthorized access to documentation is generally lower-risk than write/execute/destructive operations, though the specific sensitivity of documents could vary.
From the tool's definition Tool name 'list_instance_knowledge' and description 'List user-specific knowledge documents in your private subscribed instance' indicate a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_instance_knowledge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_instance_knowledge, this is the rule to start with:
list_instance_knowledge is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every list_instance_knowledge call is checked against it from then on.
Questions about list_instance_knowledge
List user-specific knowledge documents in your private subscribed instance. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for list_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.
list_instance_knowledge is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_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.
This server
Across the catalogue