theprotocol_getBundleManifest
Get a bundle's manifest.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getbundlemanifest.md
What theprotocol_getBundleManifest does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getBundleManifest to retrieve information from TheProtocol — Sovereign AI Agent Platform without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
bundle_id | string | Yes |
Parameters from the server's own tool schema.
Why theprotocol_getBundleManifest is rated Low
This is a straightforward data retrieval function that queries and returns manifest information about a bundle. It has no side effects, does not execute code, does not modify state, and does not involve financial transactions. The 'Get' verb and passive nature of retrieving metadata classify this as a Read operation with low severity.
From the tool's definition Tool name 'getBundleManifest' and description 'Get a bundle's manifest' indicate a retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
The rule that runs theprotocol_getBundleManifest safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TheProtocol — Sovereign AI Agent Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For theprotocol_getBundleManifest, this is the rule to start with:
theprotocol_getBundleManifest is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_getBundleManifest call is checked against it from then on.
Questions about theprotocol_getBundleManifest
Get a bundle's manifest. It is categorised as a Read tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it retrieves data without modifying state.
theprotocol_getBundleManifest accepts 1 parameter: bundle_id. Required: bundle_id. The full parameter table on this page comes from the server's own tool schema.
Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_getBundleManifest: 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 TheProtocol — Sovereign AI Agent Platform. Nothing to install.
theprotocol_getBundleManifest 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 theprotocol_getBundleManifest 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 theprotocol_getBundleManifest. 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.
theprotocol_getBundleManifest is provided by the TheProtocol — Sovereign AI Agent Platform MCP server (https://api.theprotocol.cloud/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.
Across the catalogue