Return a compact summary of cached MantisBT metadata: project count, tag count, and per-project counts of users, versions, and categories. If the cache does not exist or has expired (default TTL: 24 hours), it will automatically sync first. Use sync_metadata to force a refresh. For full lists use...
AI agents call get_metadata to retrieve information from MantisBT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries aggregate metadata about the MantisBT system. It performs no side effects, creates no data, modifies no state, and has no irreversible operations. It is a pure read operation. The automatic cache sync is a refresh mechanism that does not constitute a write or destructive action. Severity is low because misuse would only expose informational summaries without operational impact.
From the tool's definition Tool returns a 'compact summary' of cached metadata including counts of projects, tags, users, versions, and categories. Described as 'Return' operation with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Return a compact summary of cached MantisBT metadata: project count, tag count, and per-project counts of users, versions, and categories. If the cache does not exist or has expired (default TTL: 24 hours), it will automatically sync first. Use sync_metadata to force a refresh. For full lists use: list_projects (projects), get_project_users / get_project_versions / get_project_categories (per-project data), list_tags (tags). It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MantisBT MCP Server MCP server in PolicyLayer and add a rule for get_metadata: 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 MantisBT MCP Server. Nothing to install.
get_metadata 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_metadata 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_metadata. 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_metadata is provided by the MantisBT MCP Server MCP server (@dpesch/mantisbt-mcp-server). 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 →