Return Inkwell site configuration: name, domain, enabled features and connectors.
AI agents call site_info to retrieve information from Inkwell MCP Server 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 site metadata (name, domain, features, connectors) without creating, modifying, executing operations on external systems, or deleting data. It is a straightforward read operation with minimal risk, appropriate for low severity. The confidence is high because the description is clear and unambiguous about its read-only purpose.
From the tool's definition Tool description states 'Return Inkwell site configuration' — a retrieval operation with no modification or side effects. The verb 'Return' and the read-only nature of querying configuration data confirms this is information retrieval.
Attacks that exploit this kind of access
Return Inkwell site configuration: name, domain, enabled features and connectors. It is categorised as a Read tool in the Inkwell MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Inkwell MCP Server MCP server in PolicyLayer and add a rule for site_info: 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 Inkwell MCP Server. Nothing to install.
site_info 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 site_info 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 site_info. 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.
site_info is provided by the Inkwell MCP Server MCP server (mumega-com/inkwell). 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 →