suggest_templates
AI agents call suggest_templates to retrieve information from GitHub PR Template Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to suggest or retrieve PR templates based on repository context. While the description is empty, the server's stated purpose ('analyzing git changes and suggesting appropriate PR templates') and the pattern of sibling tools all performing read-only analysis operations strongly indicate this is a read operation that queries data without side effects.
From the tool's definition Tool is a sibling of other read-only analysis tools (analyze_file_changes, classify_commit_history, get_changed_modules, get_pr_template, summarize_commit_messages) that query and examine repository data without modification.
Attacks that exploit this kind of access
suggest_templates. It is categorised as a Read tool in the GitHub PR Template Tools MCP Server, which means it retrieves data without modifying state.
Register the GitHub PR Template Tools MCP server in PolicyLayer and add a rule for suggest_templates: 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 GitHub PR Template Tools. Nothing to install.
suggest_templates 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 suggest_templates 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 suggest_templates. 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.
suggest_templates is provided by the GitHub PR Template Tools MCP server (sawantudayan/github-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 →