Returns agent identity, role, permissions, and system info. ${projectHint}. ${deptHint}
AI agents call info to retrieve information from Writbase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only reads and returns data about the agent's identity, role, permissions, and system information. There are no write, execute, or destructive operations indicated. Low severity because the data returned is informational metadata, though permissions details could be mildly sensitive.
From the tool's definition 'Returns agent identity, role, permissions, and system info' — purely retrieves and returns information with no side effects
Documented attack patterns abuse exactly the kind of access info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Writbase, and nothing reaches the server without passing your rules. This is the rule we recommend for info:
{
"version": "1",
"default": "deny",
"tools": {
"info": {}
}
}info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns agent identity, role, permissions, and system info. ${projectHint}. ${deptHint}. It is categorised as a Read tool in the Writbase MCP Server, which means it retrieves data without modifying state.
Register the Writbase MCP server in PolicyLayer and add a rule for 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 Writbase. Nothing to install.
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 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 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.
info is provided by the Writbase MCP server (https://{PROJECT_REF}.supabase.co/functions/v1/mcp-server/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Writbase, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Writbase tools catalogued and risk-classified — across an index of 43,000+ MCP servers.