get_episodes
AI agents call get_episodes to retrieve information from KnowledgeSmith MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and positioning among write/destructive operations on a document editing server indicates this retrieves existing episode data without modification. This is a read operation with minimal risk—no data is created, modified, or destroyed. Low severity appropriate for query/retrieval tools.
From the tool's definition Tool name 'get_episodes' with 'get' prefix indicates retrieval operation; server context shows CRUD functionality where 'get' operations are read operations alongside write (add_document), destructive (delete_episode, delete_entity_edge), and search…
Attacks that exploit this kind of access
get_episodes. It is categorised as a Read tool in the KnowledgeSmith MCP MCP Server, which means it retrieves data without modifying state.
Register the KnowledgeSmith MCP server in PolicyLayer and add a rule for get_episodes: 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 KnowledgeSmith MCP. Nothing to install.
get_episodes 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 get_episodes 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 get_episodes. 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.
get_episodes is provided by the KnowledgeSmith MCP server (leo7nel23/knowledgesmith-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 →