Retrieve one or more MantisBT configuration options. Common option names: - "status_enum_string" — issue status values and their IDs - "priority_enum_string" — priority values - "severity_enum_string" — severity values - "resolution_enum_string" — resolution values - "reproducibility_enum_string"...
AI agents call get_config 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
options | array | Yes | Array of configuration option names to retrieve |
Parameters from the server's own tool schema.
This tool only retrieves static configuration data and enumeration values used for reference within the issue tracking system. It performs no modifications, deletions, or external operations. The blast radius of misuse is minimal—an agent could only query configuration metadata to understand available options, which poses no security or operational risk.
From the tool's definition Tool description states 'Retrieve one or more MantisBT configuration options' with examples limited to enumeration values (status_enum_string, priority_enum_string, severity_enum_string, etc.). These are read-only configuration metadata with no side effects.
Attacks that exploit this kind of access
Retrieve one or more MantisBT configuration options. Common option names: - "status_enum_string" — issue status values and their IDs - "priority_enum_string" — priority values - "severity_enum_string" — severity values - "resolution_enum_string" — resolution values - "reproducibility_enum_string" — reproducibility values - "view_state_enum_string" — view state values - "access_levels_enum_string" — access level values. It is categorised as a Read tool in the MantisBT MCP Server MCP Server, which means it retrieves data without modifying state.
get_config accepts 1 parameter: options. Required: options. The full parameter table on this page comes from the server's own tool schema.
Register the MantisBT MCP Server MCP server in PolicyLayer and add a rule for get_config: 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_config 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_config 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_config. 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_config 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 →