Get pages published to a client portal. Returns the portal page tree for a given workspace, optionally filtered to a specific page. Use list_portals first to find active portals.
AI agents call get_portal_pages to retrieve information from Fusebase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns existing portal page data without creating, modifying, deleting, or executing any operations. It is a pure read operation that queries workspace portal pages, making it a Read category tool with low severity since it only exposes existing information.
From the tool's definition Tool name 'get_portal_pages' and description 'Get pages published to a client portal. Returns the portal page tree for a given workspace' indicates data retrieval with no modification capability.
Attacks that exploit this kind of access
Get pages published to a client portal. Returns the portal page tree for a given workspace, optionally filtered to a specific page. Use list_portals first to find active portals. It is categorised as a Read tool in the Fusebase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for get_portal_pages: 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 Fusebase MCP Server. Nothing to install.
get_portal_pages 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_portal_pages 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_portal_pages. 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_portal_pages is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-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 →