AI agents call get_related to retrieve information from Wikimcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns metadata about wiki page relationships without modifying any data, executing code, or triggering external operations. It is a pure retrieval operation with no side effects, fitting the 'Read' category. The low severity reflects minimal risk from misuse—returning related pages cannot cause harm to the wiki or user data.
From the tool's definition Tool retrieves relational graph data ('Pages related to') with directional options (references, backlinks). The verb 'get' and the read-only nature of querying relationships indicates no modification or execution of operations.
Attacks that exploit this kind of access
Pages related to page. direction: out=references, in=backlinks, both=labelled. It is categorised as a Read tool in the Wikimcp MCP Server, which means it retrieves data without modifying state.
Register the Wiki MCP server in PolicyLayer and add a rule for get_related: 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 Wikimcp. Nothing to install.
get_related 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_related 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_related. 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_related is provided by the Wiki MCP server (mohith-das/wikimcp). 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 →