Process raw text and add it to the knowledge base.
AI agents use process_text to create or update resources in MyAIGist MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MyAIGist MCP environment.
This tool creates new entries in a knowledge base by processing and storing raw text. It is reversible (the sibling tool 'delete_document' indicates documents can be removed), so it is Write rather than Destructive. The severity is low because the operation only affects local knowledge management with no side effects on external systems, financial data, or system-critical resources.
From the tool's definition Tool description states it will 'add it to the knowledge base', which is a create/write operation that modifies the persistent local vector store.
Attacks that exploit this kind of access
Process raw text and add it to the knowledge base. It is categorised as a Write tool in the MyAIGist MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MyAIGist MCP server in PolicyLayer and add a rule for process_text: 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 MyAIGist MCP. Nothing to install.
process_text 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 process_text 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 process_text. 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.
process_text is provided by the MyAIGist MCP server (schwim23/myaigist_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →